Project Number Date
test_Tails_ISO_stable 6664 14 Sep 2026, 18:21

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:35.014 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:0.514
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.114
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.110
When I start Tails from USB drive "old" with network unplugged 42.095
Then the boot device has safe access rights 2.526
And Tails is running from USB drive "old" 0.202
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.550
After features/support/hooks.rb:108 0.024
Tags: @product
1:25.382
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 50.057
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 23.745
And I take note of which tps features are available 6.777
Then a Tails persistence partition exists on USB drive "old" 0.507
And I shutdown Tails and wait for the computer to power off 3.951
After features/support/hooks.rb:339 0.448
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.715
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.878
Then Tails is running from USB drive "old" 0.245
And all tps features are active 8.444
When I write some files expected to persist 1.038
# 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.325
And all persistent directories from the old Tails version have safe access rights 2.002
And I take note of which tps features are available 6.685
And I shutdown Tails and wait for the computer to power off 3.886
# 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" 11.939
After features/support/hooks.rb:339 0.096
After features/support/hooks.rb:108 0.006
Tags: @product
2:18.017
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 without a persistent partition and stopped at Tails Greeter's login screen 9.155
And I log in to a new session 14.626
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.806
And I plug USB drive "to_upgrade" 2.265
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.274
Then the running Tails is installed on USB drive "to_upgrade" 18.646
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.837
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.701
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.106
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.757
Then all tps features from the old Tails version are active 1.223
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.363
And the expected persistent files created with the old Tails version are present in the filesystem 1.181
And all persistent directories from the old Tails version have safe access rights 1.844
After features/support/hooks.rb:339 0.505
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:39.214
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 8.197
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.554
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.524
When the network is plugged 0.037
And Tor is ready 11.975
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.409
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.451
Given I shutdown Tails and wait for the computer to power off 5.544
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.704
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 8.131
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.108
# 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.137
When the network is plugged 0.029
And Tor is ready 13.470
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.307
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.655
Given I shutdown Tails and wait for the computer to power off 4.207
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.961
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.406
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.028
And Tor is ready 10.503
Then the Upgrader considers the system as up-to-date 0.103
# 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 3.265
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.355
After features/support/hooks.rb:339 0.618
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.468
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 8.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.952
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.953
After features/support/hooks.rb:339 0.722
After features/support/hooks.rb:108 0.000