Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 1 04 Jun 2026, 17:08

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:25.668 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:5.320
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.986
When I start Tails from USB drive "old" with network unplugged 46.943
Then the boot device has safe access rights 2.614
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:335 1.543
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.057
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login 54.911
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 25.013
And I take note of which tps features are available 0.327
Then a Tails persistence partition exists on USB drive "old" 0.626
And I shutdown Tails and wait for the computer to power off 6.848
After features/support/hooks.rb:335 0.273
After features/support/hooks.rb:104 0.008
Tags: @product
1:28.523
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.177
Then Tails is running from USB drive "old" 0.278
And all tps features are active 1.098
When I write some files expected to persist 1.398
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
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.985
And I take note of which tps features are available 0.143
And I shutdown Tails and wait for the computer to power off 7.916
# 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.884
After features/support/hooks.rb:335 0.315
After features/support/hooks.rb:104 0.007
Tags: @product
2:10.164
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.639
And I log in to a new session 12.709
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.265
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.172
Then the running Tails is installed on USB drive "to_upgrade" 14.269
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:335 1.983
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.152
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.132
Then all tps features from the old Tails version are active 1.082
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 2.614
And the expected persistent files created with the old Tails version are present in the filesystem 1.115
And all persistent directories from the old Tails version have safe access rights 1.856
After features/support/hooks.rb:335 0.557
After features/support/hooks.rb:104 0.006
3:42.198
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.260
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
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.260
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.021
And Tor is ready 13.257
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.414
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.065
Given I shutdown Tails and wait for the computer to power off 10.645
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.932
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.339
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.227
When the network is plugged 0.018
And Tor is ready 9.708
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.836
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.867
Given I shutdown Tails and wait for the computer to power off 4.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.059
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.143
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.017
And Tor is ready 10.088
Then the Upgrader considers the system as up-to-date 10.513
# 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.101
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.397
After features/support/hooks.rb:335 0.708
After features/support/hooks.rb:104 0.011
21.251
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.874
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.048
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.326
After features/support/hooks.rb:335 1.104
After features/support/hooks.rb:104 0.000