Project Number Date
test_Tails_ISO_stable 6417 02 Jun 2026, 11:31

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 10:55.811 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
58.372
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.054
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.225
When I start Tails from USB drive "old" with network unplugged 40.595
Then the boot device has safe access rights 2.732
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.168
After features/support/hooks.rb:335 1.385
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.932
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 51.611
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 23.957
And I take note of which tps features are available 0.311
Then a Tails persistence partition exists on USB drive "old" 0.636
And I shutdown Tails and wait for the computer to power off 8.107
After features/support/hooks.rb:335 0.394
After features/support/hooks.rb:104 0.006
Tags: @product
1:22.474
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.125
Then Tails is running from USB drive "old" 0.233
And all tps features are active 1.018
When I write some files expected to persist 1.268
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.727
And I take note of which tps features are available 0.150
And I shutdown Tails and wait for the computer to power off 7.935
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.546
After features/support/hooks.rb:335 0.349
After features/support/hooks.rb:104 0.007
Tags: @product
2:8.310
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.924
And I log in to a new session 11.670
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.729
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.095
Then the running Tails is installed on USB drive "to_upgrade" 14.420
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:335 1.983
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.382
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.138
Then all tps features from the old Tails version are active 0.876
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.286
And the expected persistent files created with the old Tails version are present in the filesystem 1.002
And all persistent directories from the old Tails version have safe access rights 1.759
After features/support/hooks.rb:335 0.860
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:34.730
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.073
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.021
And Tor is ready 12.765
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.754
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.505
Given I shutdown Tails and wait for the computer to power off 10.844
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.100
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.164
And the file system changes introduced in version 6.2~testoverlayfs are present 0.188
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.130
# 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.212
When the network is plugged 0.014
And Tor is ready 11.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.720
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.022
Given I shutdown Tails and wait for the computer to power off 7.939
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.338
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.199
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.207
When the network is plugged 0.014
And Tor is ready 11.917
Then the Upgrader considers the system as up-to-date 10.475
# 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.195
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.308
After features/support/hooks.rb:335 0.607
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.609
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.259
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.044
After features/support/hooks.rb:335 0.566
After features/support/hooks.rb:104 0.000