Project Number Date
test_Tails_ISO_21472-circumvention-settings-2 8 03 Apr 2026, 02:18

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:29.832 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.583
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.819
When I start Tails from USB drive "old" with network unplugged 50.943
Then the boot device has safe access rights 2.894
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 1.574
After features/support/hooks.rb:100 0.009
Tags: @product
1:30.816
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.141
And I start Tails from USB drive "old" with network unplugged and I login 55.515
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 25.332
And I take note of which tps features are available 0.803
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 8.165
After features/support/hooks.rb:331 0.564
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.162
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.693
Then Tails is running from USB drive "old" 0.234
And all tps features are active 1.018
When I write some files expected to persist 1.431
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 1.901
And I take note of which tps features are available 0.135
And I shutdown Tails and wait for the computer to power off 8.030
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.048
After features/support/hooks.rb:331 0.199
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.110
And I log in to a new session 14.141
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.112
And I plug USB drive "to_upgrade" 2.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.234
Then the running Tails is installed on USB drive "to_upgrade" 15.727
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 2.367
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.949
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.290
Then all tps features from the old Tails version are active 0.988
And Tails is running from USB drive "to_upgrade" 0.405
And the boot device has safe access rights 2.801
And the expected persistent files created with the old Tails version are present in the filesystem 1.182
And all persistent directories from the old Tails version have safe access rights 2.224
After features/support/hooks.rb:331 0.815
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:28.426
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.479
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.018
And Tor is ready 20.563
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.405
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.980
Given I shutdown Tails and wait for the computer to power off 20.395
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.671
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.202
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.213
When the network is plugged 0.014
And Tor is ready 20.771
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.347
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.628
Given I shutdown Tails and wait for the computer to power off 17.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.931
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 1.140
And the file system changes introduced in version 6.3~testoverlayfs are present 0.358
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.017
And Tor is ready 20.563
Then the Upgrader considers the system as up-to-date 0.102
# 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 4.148
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.427
After features/support/hooks.rb:331 1.026
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
28.034
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.639
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 19.617
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.364
After features/support/hooks.rb:331 0.739
After features/support/hooks.rb:100 0.000