Project Number Date
test_Tails_ISO_stable 6488 05 Jul 2026, 11:39

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:0.197 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:10.364
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.590
When I start Tails from USB drive "old" with network unplugged 52.581
Then the boot device has safe access rights 2.484
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.198
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.492
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 54.412
Then Tails is running from USB drive "old" 0.256
And I create a persistent partition 24.026
And I take note of which tps features are available 4.283
Then a Tails persistence partition exists on USB drive "old" 0.581
And I shutdown Tails and wait for the computer to power off 6.886
After features/support/hooks.rb:339 0.367
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.701
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.058
Then Tails is running from USB drive "old" 0.224
And all tps features are active 5.017
When I write some files expected to persist 1.284
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.351
And all persistent directories from the old Tails version have safe access rights 2.468
And I take note of which tps features are available 4.381
And I shutdown Tails and wait for the computer to power off 4.259
# 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.420
After features/support/hooks.rb:339 0.140
After features/support/hooks.rb:108 0.008
Tags: @product
2:10.378
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.074
And I log in to a new session 12.597
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.786
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.571
Then the running Tails is installed on USB drive "to_upgrade" 14.857
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.047
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.300
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.729
Then all tps features from the old Tails version are active 1.094
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 2.833
And the expected persistent files created with the old Tails version are present in the filesystem 1.234
And all persistent directories from the old Tails version have safe access rights 2.039
After features/support/hooks.rb:339 0.960
After features/support/hooks.rb:108 0.036
Tags: @product @automatic_upgrade
3:57.115
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.015
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.463
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.016
And Tor is ready 13.460
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.531
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.565
Given I shutdown Tails and wait for the computer to power off 10.854
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.827
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.275
When the network is plugged 0.033
And Tor is ready 9.804
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.487
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.698
Given I shutdown Tails and wait for the computer to power off 8.064
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.994
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.656
And the file system changes introduced in version 6.3~testoverlayfs are present 0.315
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.177
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.016
And Tor is ready 9.661
Then the Upgrader considers the system as up-to-date 10.556
# 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.347
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.487
After features/support/hooks.rb:339 0.845
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.843
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.802
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
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.016
And Tor is ready 9.002
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.682
After features/support/hooks.rb:339 0.920
After features/support/hooks.rb:108 0.000