Project Number Date
test_Tails_ISO_stable 6435 09 Jun 2026, 07:37

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:1.342 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
1:6.667
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.579
When I start Tails from USB drive "old" with network unplugged 46.698
Then the boot device has safe access rights 3.521
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.240
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:335 1.305
After features/support/hooks.rb:104 0.008
Tags: @product
1:27.819
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 56.087
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 26.189
And I take note of which tps features are available 0.364
Then a Tails persistence partition exists on USB drive "old" 0.604
And I shutdown Tails and wait for the computer to power off 4.211
After features/support/hooks.rb:335 0.518
After features/support/hooks.rb:104 0.007
Tags: @product
1:35.383
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.610
Then Tails is running from USB drive "old" 0.227
And all tps features are active 1.324
When I write some files expected to persist 1.523
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 2.437
And I take note of which tps features are available 0.192
And I shutdown Tails and wait for the computer to power off 6.994
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 13.501
After features/support/hooks.rb:335 0.453
After features/support/hooks.rb:104 0.013
Tags: @product
2:14.250
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.788
And I log in to a new session 13.705
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.838
And I plug USB drive "to_upgrade" 2.257
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.378
Then the running Tails is installed on USB drive "to_upgrade" 15.960
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:335 2.155
After features/support/hooks.rb:104 0.000
Tags: @product
1:17.726
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.962
Then all tps features from the old Tails version are active 1.197
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 3.171
And the expected persistent files created with the old Tails version are present in the filesystem 1.550
And all persistent directories from the old Tails version have safe access rights 2.429
After features/support/hooks.rb:335 0.643
After features/support/hooks.rb:104 0.019
Tags: @product @automatic_upgrade
3:56.750
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.231
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.023
And Tor is ready 13.609
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.911
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.736
Given I shutdown Tails and wait for the computer to power off 11.205
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.941
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 1.427
And the file system changes introduced in version 6.2~testoverlayfs are present 0.248
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.465
When the network is plugged 0.028
And Tor is ready 11.722
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.398
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.611
Given I shutdown Tails and wait for the computer to power off 8.560
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.594
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.147
And the file system changes introduced in version 6.3~testoverlayfs are present 0.472
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.020
And Tor is ready 11.805
Then the Upgrader considers the system as up-to-date 10.593
# 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.872
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.483
After features/support/hooks.rb:335 0.697
After features/support/hooks.rb:104 0.033
Tags: @product @automatic_upgrade
22.744
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.999
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.826
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.574
After features/support/hooks.rb:335 1.087
After features/support/hooks.rb:104 0.000