Project Number Date
test_Tails_ISO_21811-firmware-sof-2026.09.1-1 3 07 Oct 2026, 13:51

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:53.708 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:16.973
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.631
When I start Tails from USB drive "old" with network unplugged 59.566
Then the boot device has safe access rights 2.147
And Tails is running from USB drive "old" 0.147
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.446
After features/support/hooks.rb:108 0.007
Tags: @product
1:25.586
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 50.341
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 23.576
And I take note of which tps features are available 6.570
Then a Tails persistence partition exists on USB drive "old" 0.550
And I shutdown Tails and wait for the computer to power off 4.209
After features/support/hooks.rb:339 0.331
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.561
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.120
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.505
Then Tails is running from USB drive "old" 0.245
And all tps features are active 7.437
When I write some files expected to persist 1.047
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.137
And all persistence configuration files have safe access rights 0.251
And all persistent directories from the old Tails version have safe access rights 1.567
And I take note of which tps features are available 6.696
And I shutdown Tails and wait for the computer to power off 2.784
# 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.768
After features/support/hooks.rb:339 0.252
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.936
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 8.359
And I log in to a new session 12.558
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.824
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.842
Then the running Tails is installed on USB drive "to_upgrade" 18.891
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.805
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.293
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.130
Then all tps features from the old Tails version are active 1.116
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.327
And the expected persistent files created with the old Tails version are present in the filesystem 1.416
And all persistent directories from the old Tails version have safe access rights 1.966
After features/support/hooks.rb:339 0.996
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
3:52.198
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 21.834
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
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.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.305
When the network is plugged 0.046
And Tor is ready 12.748
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.120
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.028
Given I shutdown Tails and wait for the computer to power off 5.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.412
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 10.482
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
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.124
# 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.186
When the network is plugged 0.022
And Tor is ready 10.373
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.989
Given I shutdown Tails and wait for the computer to power off 3.999
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.667
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.204
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.027
And Tor is ready 10.464
Then the Upgrader considers the system as up-to-date 0.090
# 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.223
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.292
After features/support/hooks.rb:339 0.618
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
19.158
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.329
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 9.459
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.988
After features/support/hooks.rb:339 0.568
After features/support/hooks.rb:108 0.000