Project Number Date
test_Tails_ISO_stable 6121 05 Feb 2026, 11:55

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:27.340 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:19.127
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.016
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.667
When I start Tails from USB drive "old" with network unplugged 59.286
Then the boot device has safe access rights 3.136
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.081
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.202
After features/support/hooks.rb:331 3.720
After features/support/hooks.rb:100 0.008
Tags: @product
1:34.519
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 58.167
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 25.906
And I take note of which tps features are available 0.769
Then a Tails persistence partition exists on USB drive "old" 0.594
And I shutdown Tails and wait for the computer to power off 8.734
After features/support/hooks.rb:331 0.438
After features/support/hooks.rb:100 0.009
Tags: @product
1:31.397
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.881
Then Tails is running from USB drive "old" 0.264
And all tps features are active 1.174
When I write some files expected to persist 1.289
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 2.056
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 8.483
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.481
After features/support/hooks.rb:331 0.448
After features/support/hooks.rb:100 0.017
Tags: @product
2:15.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.900
And I log in to a new session 10.613
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.391
And I plug USB drive "to_upgrade" 2.250
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.372
Then the running Tails is installed on USB drive "to_upgrade" 17.012
And I unplug USB drive "to_upgrade" 0.170
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:331 2.070
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.762
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.485
Then all tps features from the old Tails version are active 1.294
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 3.140
And the expected persistent files created with the old Tails version are present in the filesystem 1.363
And all persistent directories from the old Tails version have safe access rights 2.155
After features/support/hooks.rb:331 0.939
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:11.907
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.320
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.539
When the network is plugged 0.018
And Tor is ready 14.011
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.235
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.528
Given I shutdown Tails and wait for the computer to power off 7.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.328
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.219
And the file system changes introduced in version 6.2~testoverlayfs are present 0.414
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.240
# 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.332
When the network is plugged 0.022
And Tor is ready 11.994
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.540
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.247
Given I shutdown Tails and wait for the computer to power off 8.743
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.390
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.461
And the file system changes introduced in version 6.3~testoverlayfs are present 0.489
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.017
And Tor is ready 40.175
Then the Upgrader considers the system as up-to-date 0.203
# 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.439
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:331 1.144
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
20.756
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.863
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.406
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.145
After features/support/hooks.rb:331 1.025
After features/support/hooks.rb:100 0.000