Project Number Date
test_Tails_ISO_21742-tor-browser-15.0.21 1 31 Aug 2026, 16:22

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:30.881 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:18.355
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.292
When I start Tails from USB drive "old" with network unplugged 1:0.969
Then the boot device has safe access rights 2.380
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.168
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 3.708
After features/support/hooks.rb:108 0.023
Tags: @product
1:21.733
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 48.882
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 22.636
And I take note of which tps features are available 6.799
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 2.599
After features/support/hooks.rb:339 0.604
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.588
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.651
Then Tails is running from USB drive "old" 0.214
And all tps features are active 7.463
When I write some files expected to persist 1.197
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.338
And all persistent directories from the old Tails version have safe access rights 1.561
And I take note of which tps features are available 5.680
And I shutdown Tails and wait for the computer to power off 2.512
# 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.707
After features/support/hooks.rb:339 0.222
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.560
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.108
And I log in to a new session 11.519
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.692
And I plug USB drive "to_upgrade" 2.195
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.704
Then the running Tails is installed on USB drive "to_upgrade" 18.095
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 3.534
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.526
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.728
Then all tps features from the old Tails version are active 1.040
And Tails is running from USB drive "to_upgrade" 0.219
And the boot device has safe access rights 2.089
And the expected persistent files created with the old Tails version are present in the filesystem 0.788
And all persistent directories from the old Tails version have safe access rights 1.568
After features/support/hooks.rb:339 0.664
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:39.051
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.145
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.203
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.047
And Tor is ready 12.550
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.912
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.247
Given I shutdown Tails and wait for the computer to power off 7.043
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.619
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.222
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
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.111
# 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.155
When the network is plugged 0.034
And Tor is ready 10.442
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.319
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.640
Given I shutdown Tails and wait for the computer to power off 3.983
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.322
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.943
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.059
# 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.090
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.165
When the network is plugged 0.023
And Tor is ready 10.233
Then the Upgrader considers the system as up-to-date 10.434
# 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.470
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.325
After features/support/hooks.rb:339 0.756
After features/support/hooks.rb:108 0.041
Tags: @product @automatic_upgrade
19.065
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.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 8.732
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.926
After features/support/hooks.rb:339 0.633
After features/support/hooks.rb:108 0.000