Project Number Date
test_Tails_ISO_stable 6113 02 Feb 2026, 12:46

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 16:25.338 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
2:37.021
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 51.994
When I start Tails from USB drive "old" with network unplugged 1:39.358
Then the boot device has safe access rights 3.494
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:331 10.178
After features/support/hooks.rb:100 0.088
Tags: @product
2:39.055
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:21.949
Then Tails is running from USB drive "old" 1.557
And I create a persistent partition 1:5.486
And I take note of which tps features are available 1.720
Then a Tails persistence partition exists on USB drive "old" 0.679
And I shutdown Tails and wait for the computer to power off 7.480
After features/support/hooks.rb:331 0.196
After features/support/hooks.rb:100 0.027
Tags: @product
1:53.039
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:18.996
Then Tails is running from USB drive "old" 0.729
And all tps features are active 1.828
When I write some files expected to persist 1.541
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.532
And all persistent directories from the old Tails version have safe access rights 2.417
And I take note of which tps features are available 0.435
And I shutdown Tails and wait for the computer to power off 7.645
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.449
After features/support/hooks.rb:331 0.477
After features/support/hooks.rb:100 0.009
Tags: @product
2:52.110
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.347
And I log in to a new session 15.258
And I clone USB drive "old" to a new USB drive "to_upgrade" 17.554
And I plug USB drive "to_upgrade" 1.831
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.757
Then the running Tails is installed on USB drive "to_upgrade" 19.993
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:331 2.366
After features/support/hooks.rb:100 0.000
Tags: @product
1:27.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:18.661
Then all tps features from the old Tails version are active 1.568
And Tails is running from USB drive "to_upgrade" 0.354
And the boot device has safe access rights 2.987
And the expected persistent files created with the old Tails version are present in the filesystem 1.371
And all persistent directories from the old Tails version have safe access rights 2.264
After features/support/hooks.rb:331 1.046
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:32.319
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.132
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.269
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.104
And Tor is ready 14.783
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.623
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.857
Given I shutdown Tails and wait for the computer to power off 11.490
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.582
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.065
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.219
# 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.054
And Tor is ready 12.210
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.605
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.820
Given I shutdown Tails and wait for the computer to power off 9.225
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.630
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.195
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.058
And Tor is ready 11.685
Then the Upgrader considers the system as up-to-date 0.120
# 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 5.903
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.447
After features/support/hooks.rb:331 0.950
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
24.413
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.947
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
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.067
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 9.870
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.145
After features/support/hooks.rb:331 0.932
After features/support/hooks.rb:100 0.000