Project Number Date
test_Tails_ISO_21619-tor-browser-15.0.16 5 15 Jun 2026, 09:55

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 12:11.724 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.225
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.695
When I start Tails from USB drive "old" with network unplugged 46.998
Then the boot device has safe access rights 2.593
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:339 3.873
After features/support/hooks.rb:108 0.022
Tags: @product
1:34.772
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.133
And I start Tails from USB drive "old" with network unplugged and I login 55.704
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 25.874
And I take note of which tps features are available 5.068
Then a Tails persistence partition exists on USB drive "old" 0.643
And I shutdown Tails and wait for the computer to power off 7.113
After features/support/hooks.rb:339 0.615
After features/support/hooks.rb:108 0.018
Tags: @product
1:41.498
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.128
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.895
Then Tails is running from USB drive "old" 0.266
And all tps features are active 5.608
When I write some files expected to persist 1.408
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.081
And I take note of which tps features are available 3.904
And I shutdown Tails and wait for the computer to power off 8.474
# 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.147
After features/support/hooks.rb:339 0.350
After features/support/hooks.rb:108 0.020
Tags: @product
2:11.158
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.405
And I log in to a new session 12.385
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.847
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.662
Then the running Tails is installed on USB drive "to_upgrade" 15.311
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:339 2.150
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.883
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.033
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.489
Then all tps features from the old Tails version are active 0.957
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.731
And the expected persistent files created with the old Tails version are present in the filesystem 1.342
And all persistent directories from the old Tails version have safe access rights 1.961
After features/support/hooks.rb:339 0.883
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
4:0.545
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.849
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.014
And Tor is ready 13.804
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.017
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.614
Given I shutdown Tails and wait for the computer to power off 10.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.966
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.411
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.235
When the network is plugged 0.014
And Tor is ready 10.177
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.794
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.097
Given I shutdown Tails and wait for the computer to power off 4.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.550
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.103
And the file system changes introduced in version 6.3~testoverlayfs are present 0.411
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.177
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.488
When the network is plugged 0.014
And Tor is ready 10.387
Then the Upgrader considers the system as up-to-date 10.680
# 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.385
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.436
After features/support/hooks.rb:339 0.904
After features/support/hooks.rb:108 0.040
Tags: @product @automatic_upgrade
21.640
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.837
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.865
After features/support/hooks.rb:339 0.605
After features/support/hooks.rb:108 0.000