Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 10 10 Jun 2026, 13:30

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:59.221 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:14.436
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.991
When I start Tails from USB drive "old" with network unplugged 55.898
Then the boot device has safe access rights 2.709
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:335 1.588
After features/support/hooks.rb:104 0.007
Tags: @product
1:30.912
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 55.418
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 26.883
And I take note of which tps features are available 0.485
Then a Tails persistence partition exists on USB drive "old" 0.842
And I shutdown Tails and wait for the computer to power off 6.989
After features/support/hooks.rb:335 0.500
After features/support/hooks.rb:104 0.007
Tags: @product
1:28.254
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.693
Then Tails is running from USB drive "old" 0.227
And all tps features are active 1.183
When I write some files expected to persist 1.356
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.351
And all persistent directories from the old Tails version have safe access rights 1.877
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 4.563
# 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.563
After features/support/hooks.rb:335 0.573
After features/support/hooks.rb:104 0.008
Tags: @product
2:12.650
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.835
And I log in to a new session 12.330
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.782
And I plug USB drive "to_upgrade" 2.302
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.518
Then the running Tails is installed on USB drive "to_upgrade" 16.543
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:335 2.052
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.301
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.022
Then all tps features from the old Tails version are active 1.417
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.108
And the expected persistent files created with the old Tails version are present in the filesystem 1.302
And all persistent directories from the old Tails version have safe access rights 2.052
After features/support/hooks.rb:335 0.995
After features/support/hooks.rb:104 0.030
Tags: @product @automatic_upgrade
3:55.294
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.565
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.033
And Tor is ready 13.795
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.503
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.300
Given I shutdown Tails and wait for the computer to power off 11.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.471
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.278
And the file system changes introduced in version 6.2~testoverlayfs are present 0.450
And only the 6.2~testoverlayfs SquashFS delta is installed 0.093
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.284
When the network is plugged 0.016
And Tor is ready 10.270
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.188
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.806
Given I shutdown Tails and wait for the computer to power off 8.223
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.091
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.219
And the file system changes introduced in version 6.3~testoverlayfs are present 0.412
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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.017
And Tor is ready 12.252
Then the Upgrader considers the system as up-to-date 10.657
# 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.927
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.424
After features/support/hooks.rb:335 0.876
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
22.371
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.648
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.607
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.726
After features/support/hooks.rb:335 1.048
After features/support/hooks.rb:104 0.000