Project Number Date
test_Tails_ISO_stable 6151 17 Feb 2026, 13:10

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:28.587 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:48.560
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.583
When I start Tails from USB drive "old" with network unplugged 1:29.134
Then the boot device has safe access rights 2.931
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.102
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:331 1.735
After features/support/hooks.rb:100 0.010
Tags: @product
1:34.405
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 59.811
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 24.924
And I take note of which tps features are available 0.780
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 7.995
After features/support/hooks.rb:331 0.502
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.041
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.079
Then Tails is running from USB drive "old" 0.347
And all tps features are active 1.208
When I write some files expected to persist 1.507
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 2.074
And I take note of which tps features are available 0.210
And I shutdown Tails and wait for the computer to power off 8.026
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.953
After features/support/hooks.rb:331 0.253
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.784
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 9.166
And I log in to a new session 14.047
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.798
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.351
Then the running Tails is installed on USB drive "to_upgrade" 17.833
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:331 6.999
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.500
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.012
Then all tps features from the old Tails version are active 1.034
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 2.802
And the expected persistent files created with the old Tails version are present in the filesystem 1.231
And all persistent directories from the old Tails version have safe access rights 2.029
After features/support/hooks.rb:331 0.743
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
3:43.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 8.580
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.121
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.018
And Tor is ready 16.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.059
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.802
Given I shutdown Tails and wait for the computer to power off 10.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.246
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.186
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.203
# 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.249
When the network is plugged 0.026
And Tor is ready 10.608
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.055
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.387
Given I shutdown Tails and wait for the computer to power off 4.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.195
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.186
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.015
And Tor is ready 10.194
Then the Upgrader considers the system as up-to-date 10.569
# 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.109
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.083
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
20.445
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 7.704
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
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.111
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 10.484
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.776
After features/support/hooks.rb:331 0.788
After features/support/hooks.rb:100 0.000