Project Number Date
test_Tails_ISO_stable 6161 23 Feb 2026, 14:52

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 13:16.979 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:39.194
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.680
When I start Tails from USB drive "old" with network unplugged 1:21.273
Then the boot device has safe access rights 2.527
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.697
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.721
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 50.842
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 24.407
And I take note of which tps features are available 0.673
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 7.938
After features/support/hooks.rb:331 0.599
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.488
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.903
Then Tails is running from USB drive "old" 0.298
And all tps features are active 1.081
When I write some files expected to persist 1.235
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.293
And all persistent directories from the old Tails version have safe access rights 2.023
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 7.973
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.247
After features/support/hooks.rb:331 0.358
After features/support/hooks.rb:100 0.007
Tags: @product
2:29.416
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 without a persistent partition and stopped at Tails Greeter's login screen 8.374
And I log in to a new session 13.771
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.790
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.315
Then the running Tails is installed on USB drive "to_upgrade" 17.628
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:331 3.440
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.867
Then all tps features from the old Tails version are active 0.998
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 2.609
And the expected persistent files created with the old Tails version are present in the filesystem 1.161
And all persistent directories from the old Tails version have safe access rights 1.840
After features/support/hooks.rb:331 0.857
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:32.422
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.989
And no SquashFS delta is installed 0.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.529
When the network is plugged 0.017
And Tor is ready 20.863
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.353
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.134
Given I shutdown Tails and wait for the computer to power off 20.104
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.209
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.262
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
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.140
# 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.214
When the network is plugged 0.018
And Tor is ready 20.223
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.418
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.384
Given I shutdown Tails and wait for the computer to power off 18.662
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.037
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 1.198
And the file system changes introduced in version 6.3~testoverlayfs are present 0.350
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.018
And Tor is ready 20.141
Then the Upgrader considers the system as up-to-date 0.098
# 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.381
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.323
After features/support/hooks.rb:331 1.042
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
34.887
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.327
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 26.842
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.380
After features/support/hooks.rb:331 1.017
After features/support/hooks.rb:100 0.000