Project Number Date
test_Tails_ISO_devel 4601 08 Sep 2026, 07:41

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 10:54.722 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:9.009
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.124
When I start Tails from USB drive "old" with network unplugged 51.315
Then the boot device has safe access rights 2.889
And Tails is running from USB drive "old" 0.181
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.137
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.123
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.819
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 45.251
Then Tails is running from USB drive "old" 0.185
And I create a persistent partition 22.821
And I take note of which tps features are available 6.398
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 2.554
After features/support/hooks.rb:339 0.521
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.257
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.768
Then Tails is running from USB drive "old" 0.265
And all tps features are active 6.904
When I write some files expected to persist 1.035
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.141
And all persistence configuration files have safe access rights 0.272
And all persistent directories from the old Tails version have safe access rights 1.336
And I take note of which tps features are available 5.620
And I shutdown Tails and wait for the computer to power off 2.646
# 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.187
After features/support/hooks.rb:339 0.544
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.629
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 without a persistent partition and stopped at Tails Greeter's login screen 8.111
And I log in to a new session 10.905
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.599
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.539
Then the running Tails is installed on USB drive "to_upgrade" 15.976
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 1.567
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.809
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.497
Then all tps features from the old Tails version are active 1.146
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 2.108
And the expected persistent files created with the old Tails version are present in the filesystem 1.003
And all persistent directories from the old Tails version have safe access rights 1.660
After features/support/hooks.rb:339 0.824
After features/support/hooks.rb:108 0.005
3:28.285
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.016
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.167
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.039
And Tor is ready 11.265
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.939
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.578
Given I shutdown Tails and wait for the computer to power off 5.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.041
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.341
And the file system changes introduced in version 6.2~testoverlayfs are present 0.153
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.089
# 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.179
When the network is plugged 0.031
And Tor is ready 10.315
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.334
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.473
Given I shutdown Tails and wait for the computer to power off 2.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 57.895
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.463
And the file system changes introduced in version 6.3~testoverlayfs are present 0.230
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.089
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.158
When the network is plugged 0.031
And Tor is ready 9.981
Then the Upgrader considers the system as up-to-date 10.387
# 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.099
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.277
After features/support/hooks.rb:339 1.010
After features/support/hooks.rb:108 0.014
17.911
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.806
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.174
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 7.896
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.915
After features/support/hooks.rb:339 0.765
After features/support/hooks.rb:108 0.000