Project Number Date
test_Tails_ISO_stable 6178 28 Feb 2026, 11:33

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:16.521 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:15.960
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.217
When I start Tails from USB drive "old" with network unplugged 58.576
Then the boot device has safe access rights 2.474
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 1.410
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.852
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 53.279
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 23.741
And I take note of which tps features are available 0.674
Then a Tails persistence partition exists on USB drive "old" 0.583
And I shutdown Tails and wait for the computer to power off 4.263
After features/support/hooks.rb:331 0.494
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.699
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.468
Then Tails is running from USB drive "old" 0.261
And all tps features are active 1.214
When I write some files expected to persist 1.286
# 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.455
And all persistent directories from the old Tails version have safe access rights 1.927
And I take note of which tps features are available 0.139
And I shutdown Tails and wait for the computer to power off 7.911
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.792
After features/support/hooks.rb:331 0.119
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.910
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 without a persistent partition and stopped at Tails Greeter's login screen 8.176
And I log in to a new session 11.375
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.729
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.916
Then the running Tails is installed on USB drive "to_upgrade" 15.182
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:331 2.007
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.354
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.416
Then all tps features from the old Tails version are active 0.904
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.821
And the expected persistent files created with the old Tails version are present in the filesystem 1.053
And all persistent directories from the old Tails version have safe access rights 1.879
After features/support/hooks.rb:331 0.933
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
4:29.673
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.037
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.015
And Tor is ready 19.398
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.355
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.575
Given I shutdown Tails and wait for the computer to power off 19.834
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.016
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.084
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.196
When the network is plugged 0.022
And Tor is ready 21.449
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.358
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.772
Given I shutdown Tails and wait for the computer to power off 17.152
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.249
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.108
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.045
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.014
And Tor is ready 20.828
Then the Upgrader considers the system as up-to-date 0.093
# 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 3.688
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:331 0.842
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
25.070
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.617
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 16.697
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.382
After features/support/hooks.rb:331 0.634
After features/support/hooks.rb:100 0.000