Project Number Date
test_Tails_ISO_21765-tor-browser-15.0.23 2 14 Sep 2026, 15:50

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:11.090 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
54.255
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 13.529
When I start Tails from USB drive "old" with network unplugged 36.994
Then the boot device has safe access rights 2.014
And Tails is running from USB drive "old" 0.159
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.151
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.401
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.433
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.127
And I start Tails from USB drive "old" with network unplugged and I login 49.028
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 23.430
And I take note of which tps features are available 8.406
Then a Tails persistence partition exists on USB drive "old" 0.453
And I shutdown Tails and wait for the computer to power off 2.757
After features/support/hooks.rb:339 0.440
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.683
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.559
Then Tails is running from USB drive "old" 0.234
And all tps features are active 9.074
When I write some files expected to persist 1.349
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 1.671
And I take note of which tps features are available 9.258
And I shutdown Tails and wait for the computer to power off 2.609
# 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.375
After features/support/hooks.rb:339 0.166
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.974
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.240
And I log in to a new session 13.027
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.793
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.458
Then the running Tails is installed on USB drive "to_upgrade" 18.001
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.842
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.226
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.976
Then all tps features from the old Tails version are active 1.119
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 2.271
And the expected persistent files created with the old Tails version are present in the filesystem 0.993
And all persistent directories from the old Tails version have safe access rights 1.555
After features/support/hooks.rb:339 0.937
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:30.299
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.342
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.185
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.027
And Tor is ready 11.895
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.541
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.325
Given I shutdown Tails and wait for the computer to power off 5.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.240
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 7.423
And the file system changes introduced in version 6.2~testoverlayfs are present 0.167
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.205
When the network is plugged 0.027
And Tor is ready 10.370
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.522
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.486
Given I shutdown Tails and wait for the computer to power off 5.070
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.541
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.405
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.025
And Tor is ready 10.468
Then the Upgrader considers the system as up-to-date 0.092
# 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.642
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 0.966
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
19.219
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.048
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.041
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.035
And Tor is ready 9.839
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.019
After features/support/hooks.rb:339 0.895
After features/support/hooks.rb:108 0.000