Project Number Date
test_Tails_ISO_21798-fix-new-identity-test 1 29 Sep 2026, 18: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 11:54.955 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:19.415
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 14.105
When I start Tails from USB drive "old" with network unplugged 1:0.934
Then the boot device has safe access rights 2.618
And Tails is running from USB drive "old" 0.204
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 1.305
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.822
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.117
And I start Tails from USB drive "old" with network unplugged and I login 50.457
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 24.028
And I take note of which tps features are available 7.169
Then a Tails persistence partition exists on USB drive "old" 0.620
And I shutdown Tails and wait for the computer to power off 5.219
After features/support/hooks.rb:339 0.556
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.809
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.274
Then Tails is running from USB drive "old" 0.241
And all tps features are active 7.391
When I write some files expected to persist 1.302
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.353
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 2.059
And I take note of which tps features are available 7.411
And I shutdown Tails and wait for the computer to power off 4.103
# 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.229
After features/support/hooks.rb:339 0.616
After features/support/hooks.rb:108 0.020
Tags: @product
2:20.773
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 9.428
And I log in to a new session 13.845
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.643
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.905
Then the running Tails is installed on USB drive "to_upgrade" 20.414
And I unplug USB drive "to_upgrade" 0.161
And I unplug USB drive "__internal" 0.164
After features/support/hooks.rb:339 2.025
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.353
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.474
Then all tps features from the old Tails version are active 1.092
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 2.454
And the expected persistent files created with the old Tails version are present in the filesystem 1.105
And all persistent directories from the old Tails version have safe access rights 1.884
After features/support/hooks.rb:339 0.917
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
3:33.880
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.826
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.341
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.336
When the network is plugged 0.023
And Tor is ready 13.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.731
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.342
Given I shutdown Tails and wait for the computer to power off 5.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.126
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.605
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
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.120
# 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.201
When the network is plugged 0.038
And Tor is ready 9.710
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.076
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.266
Given I shutdown Tails and wait for the computer to power off 2.755
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.068
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.272
And the file system changes introduced in version 6.3~testoverlayfs are present 0.332
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.035
And Tor is ready 10.205
Then the Upgrader considers the system as up-to-date 0.078
# 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.482
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 1.067
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.899
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.753
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.827
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.999
After features/support/hooks.rb:339 0.860
After features/support/hooks.rb:108 0.000