Project Number Date
test_Tails_ISO_post-rm-7.11 1 20 Aug 2026, 13:57

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:4.429 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:22.242
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.034
When I start Tails from USB drive "old" with network unplugged 1:5.481
Then the boot device has safe access rights 1.998
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 1.909
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.733
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 47.772
Then Tails is running from USB drive "old" 0.198
And I create a persistent partition 23.756
And I take note of which tps features are available 6.793
Then a Tails persistence partition exists on USB drive "old" 0.579
And I shutdown Tails and wait for the computer to power off 2.553
After features/support/hooks.rb:339 0.581
After features/support/hooks.rb:108 0.007
Tags: @product
1:33.241
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.528
Then Tails is running from USB drive "old" 0.259
And all tps features are active 7.531
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.159
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 1.828
And I take note of which tps features are available 6.300
And I shutdown Tails and wait for the computer to power off 2.566
# 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.319
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.500
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 9.229
And I log in to a new session 12.662
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.981
And I plug USB drive "to_upgrade" 2.333
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.904
Then the running Tails is installed on USB drive "to_upgrade" 20.132
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.108
After features/support/hooks.rb:339 3.616
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.626
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.532
Then all tps features from the old Tails version are active 1.101
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 2.941
And the expected persistent files created with the old Tails version are present in the filesystem 1.092
And all persistent directories from the old Tails version have safe access rights 1.559
After features/support/hooks.rb:339 0.564
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
3:59.146
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.533
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.322
When the network is plugged 0.041
And Tor is ready 12.492
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.326
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.469
Given I shutdown Tails and wait for the computer to power off 7.011
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.495
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 10.416
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.233
When the network is plugged 0.046
And Tor is ready 10.784
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.831
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.810
Given I shutdown Tails and wait for the computer to power off 5.107
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.979
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.188
And the file system changes introduced in version 6.3~testoverlayfs are present 0.370
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.036
And Tor is ready 10.338
Then the Upgrader considers the system as up-to-date 10.397
# 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.073
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.308
After features/support/hooks.rb:339 0.764
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
18.938
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.026
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
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.055
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.720
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.864
After features/support/hooks.rb:339 0.775
After features/support/hooks.rb:108 0.000