Project Number Date
test_Tails_ISO_stable 6126 07 Feb 2026, 11:56

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:14.616 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.438
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.742
When I start Tails from USB drive "old" with network unplugged 58.563
Then the boot device has safe access rights 3.218
And Tails is running from USB drive "old" 0.317
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.260
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:331 3.682
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 58.787
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 26.341
And I take note of which tps features are available 1.115
Then a Tails persistence partition exists on USB drive "old" 0.700
And I shutdown Tails and wait for the computer to power off 4.370
After features/support/hooks.rb:331 0.215
After features/support/hooks.rb:100 0.008
Tags: @product
1:34.372
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.456
Then Tails is running from USB drive "old" 0.218
And all tps features are active 1.093
When I write some files expected to persist 1.352
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 2.341
And I take note of which tps features are available 0.241
And I shutdown Tails and wait for the computer to power off 8.701
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.342
After features/support/hooks.rb:331 0.524
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.270
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.649
And I log in to a new session 12.350
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.036
And I plug USB drive "to_upgrade" 2.283
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.087
Then the running Tails is installed on USB drive "to_upgrade" 17.565
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:331 3.364
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.407
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.120
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.281
Then all tps features from the old Tails version are active 0.956
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.497
And the expected persistent files created with the old Tails version are present in the filesystem 1.167
And all persistent directories from the old Tails version have safe access rights 2.134
After features/support/hooks.rb:331 0.954
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
3:56.849
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.263
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.028
And Tor is ready 12.967
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.083
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.392
Given I shutdown Tails and wait for the computer to power off 11.712
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.773
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.077
And the file system changes introduced in version 6.2~testoverlayfs are present 0.251
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.014
And Tor is ready 11.931
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.185
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.977
Given I shutdown Tails and wait for the computer to power off 8.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.224
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.552
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.017
And Tor is ready 10.076
Then the Upgrader considers the system as up-to-date 10.868
# 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.209
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.425
After features/support/hooks.rb:331 1.062
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
20.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.025
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.911
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.256
After features/support/hooks.rb:331 0.620
After features/support/hooks.rb:100 0.000