Project Number Date
test_Tails_ISO_stable 6355 06 May 2026, 11:17

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 12:3.566 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
58.006
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.403
When I start Tails from USB drive "old" with network unplugged 40.291
Then the boot device has safe access rights 2.576
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.572
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.051
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 51.948
Then Tails is running from USB drive "old" 0.273
And I create a persistent partition 23.600
And I take note of which tps features are available 0.726
Then a Tails persistence partition exists on USB drive "old" 0.615
And I shutdown Tails and wait for the computer to power off 7.837
After features/support/hooks.rb:331 0.355
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.347
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.078
Then Tails is running from USB drive "old" 0.285
And all tps features are active 0.985
When I write some files expected to persist 1.226
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.506
And all persistent directories from the old Tails version have safe access rights 1.983
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 7.912
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.971
After features/support/hooks.rb:331 0.479
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.242
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.983
And I log in to a new session 12.389
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.658
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.832
Then the running Tails is installed on USB drive "to_upgrade" 15.872
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 1.826
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.909
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.930
Then all tps features from the old Tails version are active 1.008
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.502
And the expected persistent files created with the old Tails version are present in the filesystem 1.105
And all persistent directories from the old Tails version have safe access rights 2.050
After features/support/hooks.rb:331 0.787
After features/support/hooks.rb:100 0.007
4:32.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.239
And no SquashFS delta is installed 0.182
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.021
And Tor is ready 22.891
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.816
Given I shutdown Tails and wait for the computer to power off 20.018
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.836
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.075
And the file system changes introduced in version 6.2~testoverlayfs are present 0.190
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.018
And Tor is ready 21.323
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.374
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.944
Given I shutdown Tails and wait for the computer to power off 17.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.588
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.112
And the file system changes introduced in version 6.3~testoverlayfs are present 0.335
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.013
And Tor is ready 20.682
Then the Upgrader considers the system as up-to-date 0.152
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 4.263
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.420
After features/support/hooks.rb:331 1.011
After features/support/hooks.rb:100 0.011
25.456
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.472
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 17.168
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.397
After features/support/hooks.rb:331 0.746
After features/support/hooks.rb:100 0.000