Project Number Date
test_Tails_ISO_21318-tor-browser-16.0 73 16 Aug 2026, 08:00

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:2.909 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
59.002
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.897
When I start Tails from USB drive "old" with network unplugged 42.324
Then the boot device has safe access rights 2.066
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.151
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.517
After features/support/hooks.rb:108 0.023
Tags: @product
1:20.318
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 46.242
Then Tails is running from USB drive "old" 0.193
And I create a persistent partition 22.049
And I take note of which tps features are available 6.217
Then a Tails persistence partition exists on USB drive "old" 0.519
And I shutdown Tails and wait for the computer to power off 5.009
After features/support/hooks.rb:339 0.519
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.129
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.218
Then Tails is running from USB drive "old" 0.174
And all tps features are active 6.401
When I write some files expected to persist 1.012
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.113
And all persistence configuration files have safe access rights 0.223
And all persistent directories from the old Tails version have safe access rights 1.651
And I take note of which tps features are available 5.845
And I shutdown Tails and wait for the computer to power off 2.537
# 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" 10.856
After features/support/hooks.rb:339 0.139
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.519
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 without a persistent partition and stopped at Tails Greeter's login screen 8.376
And I log in to a new session 10.115
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.581
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.187
Then the running Tails is installed on USB drive "to_upgrade" 17.776
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.714
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.491
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.908
Then all tps features from the old Tails version are active 1.026
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 1.984
And the expected persistent files created with the old Tails version are present in the filesystem 0.738
And all persistent directories from the old Tails version have safe access rights 1.539
After features/support/hooks.rb:339 0.740
After features/support/hooks.rb:108 0.019
3:42.979
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 with a persistent partition enabled and logged in 21.299
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.175
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.373
When the network is plugged 0.034
And Tor is ready 12.694
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.436
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.547
Given I shutdown Tails and wait for the computer to power off 5.403
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.787
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.417
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.106
# 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.150
When the network is plugged 0.028
And Tor is ready 11.145
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.323
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.622
Given I shutdown Tails and wait for the computer to power off 2.657
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.846
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.895
And the file system changes introduced in version 6.3~testoverlayfs are present 0.284
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.081
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.022
And Tor is ready 10.036
Then the Upgrader considers the system as up-to-date 10.374
# 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 3.190
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.274
After features/support/hooks.rb:339 0.832
After features/support/hooks.rb:108 0.010
18.468
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 with a persistent partition enabled and logged in 7.856
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.055
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.329
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.904
After features/support/hooks.rb:339 0.745
After features/support/hooks.rb:108 0.000