Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 38 11 Jul 2026, 08: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:38.026 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:3.849
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.742
When I start Tails from USB drive "old" with network unplugged 45.806
Then the boot device has safe access rights 2.531
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.724
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.449
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login 52.131
Then Tails is running from USB drive "old" 0.256
And I create a persistent partition 25.213
And I take note of which tps features are available 4.232
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 7.975
After features/support/hooks.rb:339 0.435
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.589
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.083
Then Tails is running from USB drive "old" 0.221
And all tps features are active 4.549
When I write some files expected to persist 1.195
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.269
And all persistent directories from the old Tails version have safe access rights 2.088
And I take note of which tps features are available 3.872
And I shutdown Tails and wait for the computer to power off 4.093
# 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" 11.946
After features/support/hooks.rb:339 0.282
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.508
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 without a persistent partition and stopped at Tails Greeter's login screen 8.281
And I log in to a new session 13.171
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.916
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.282
Then the running Tails is installed on USB drive "to_upgrade" 15.369
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 2.220
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.430
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.733
Then all tps features from the old Tails version are active 0.956
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.561
And the expected persistent files created with the old Tails version are present in the filesystem 1.030
And all persistent directories from the old Tails version have safe access rights 1.881
After features/support/hooks.rb:339 0.797
After features/support/hooks.rb:108 0.005
3:52.625
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 with a persistent partition enabled and logged in 8.121
And no SquashFS delta is installed 0.070
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.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.366
When the network is plugged 0.020
And Tor is ready 12.295
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.004
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.240
Given I shutdown Tails and wait for the computer to power off 9.455
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.141
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.572
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# 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.199
When the network is plugged 0.040
And Tor is ready 10.008
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.105
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.576
Given I shutdown Tails and wait for the computer to power off 7.940
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.177
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.700
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.016
And Tor is ready 10.853
Then the Upgrader considers the system as up-to-date 10.503
# 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.214
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.335
After features/support/hooks.rb:339 0.773
After features/support/hooks.rb:108 0.028
19.572
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 with a persistent partition enabled and logged in 7.726
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 10.456
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.038
After features/support/hooks.rb:339 0.623
After features/support/hooks.rb:108 0.000