Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 20 21 Jun 2026, 08:15

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:52.239 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:15.541
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.040
Given a computer 0.115
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.291
When I start Tails from USB drive "old" with network unplugged 57.616
Then the boot device has safe access rights 2.756
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.159
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:339 1.401
After features/support/hooks.rb:108 0.017
Tags: @product
1:29.879
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login 51.734
Then Tails is running from USB drive "old" 0.256
And I create a persistent partition 24.671
And I take note of which tps features are available 4.233
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 8.329
After features/support/hooks.rb:339 0.454
After features/support/hooks.rb:108 0.018
Tags: @product
1:34.853
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.971
Then Tails is running from USB drive "old" 0.230
And all tps features are active 4.605
When I write some files expected to persist 1.408
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 1.816
And I take note of which tps features are available 3.734
And I shutdown Tails and wait for the computer to power off 8.426
# 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.082
After features/support/hooks.rb:339 0.508
After features/support/hooks.rb:108 0.018
Tags: @product
2:10.954
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.330
And I log in to a new session 12.837
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.761
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.954
Then the running Tails is installed on USB drive "to_upgrade" 14.531
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.199
After features/support/hooks.rb:339 2.069
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.393
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.736
Then all tps features from the old Tails version are active 0.975
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.468
And the expected persistent files created with the old Tails version are present in the filesystem 1.015
And all persistent directories from the old Tails version have safe access rights 1.765
After features/support/hooks.rb:339 0.834
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:51.118
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.275
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.292
When the network is plugged 0.016
And Tor is ready 11.992
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.376
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.516
Given I shutdown Tails and wait for the computer to power off 9.681
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.685
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.706
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
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.154
# 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.219
When the network is plugged 0.017
And Tor is ready 9.871
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.210
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.572
Given I shutdown Tails and wait for the computer to power off 8.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.241
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.754
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.177
When the network is plugged 0.019
And Tor is ready 10.859
Then the Upgrader considers the system as up-to-date 10.622
# 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.369
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.350
After features/support/hooks.rb:339 0.866
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
19.497
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.782
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.189
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.986
After features/support/hooks.rb:339 0.709
After features/support/hooks.rb:108 0.000