Project Number Date
test_Tails_ISO_stable 6399 22 May 2026, 12:15

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 11:50.743 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:4.346
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.244
When I start Tails from USB drive "old" with network unplugged 45.114
Then the boot device has safe access rights 3.122
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:335 3.748
After features/support/hooks.rb:104 0.006
Tags: @product
1:30.657
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 55.736
Then Tails is running from USB drive "old" 0.374
And I create a persistent partition 25.338
And I take note of which tps features are available 0.362
Then a Tails persistence partition exists on USB drive "old" 0.516
And I shutdown Tails and wait for the computer to power off 8.257
After features/support/hooks.rb:335 0.227
After features/support/hooks.rb:104 0.008
Tags: @product
1:31.984
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.296
Then Tails is running from USB drive "old" 0.454
And all tps features are active 1.434
When I write some files expected to persist 1.325
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.308
And all persistent directories from the old Tails version have safe access rights 1.820
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 8.305
# 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" 12.605
After features/support/hooks.rb:335 0.382
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.594
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 without a persistent partition and stopped at Tails Greeter's login screen 7.966
And I log in to a new session 13.047
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.887
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.374
Then the running Tails is installed on USB drive "to_upgrade" 16.812
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.292
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.568
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.381
Then all tps features from the old Tails version are active 1.144
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 3.136
And the expected persistent files created with the old Tails version are present in the filesystem 1.335
And all persistent directories from the old Tails version have safe access rights 2.248
After features/support/hooks.rb:335 0.671
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:54.668
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.227
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.014
And Tor is ready 12.873
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.860
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.714
Given I shutdown Tails and wait for the computer to power off 10.036
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.347
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.347
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.225
When the network is plugged 0.012
And Tor is ready 11.548
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.601
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.462
Given I shutdown Tails and wait for the computer to power off 8.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.868
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.213
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.019
And Tor is ready 11.280
Then the Upgrader considers the system as up-to-date 10.646
# 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.885
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.843
After features/support/hooks.rb:335 0.979
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
19.923
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.696
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
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 10.409
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.477
After features/support/hooks.rb:335 0.928
After features/support/hooks.rb:104 0.000