Project Number Date
test_Tails_ISO_stable 6388 20 May 2026, 11:32

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 11:31.552 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:12.355
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.290
When I start Tails from USB drive "old" with network unplugged 54.153
Then the boot device has safe access rights 2.976
And Tails is running from USB drive "old" 0.389
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:335 3.732
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.144
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 53.819
Then Tails is running from USB drive "old" 0.450
And I create a persistent partition 24.912
And I take note of which tps features are available 0.362
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 7.994
After features/support/hooks.rb:335 0.168
After features/support/hooks.rb:104 0.006
Tags: @product
1:30.226
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.563
Then Tails is running from USB drive "old" 0.326
And all tps features are active 1.098
When I write some files expected to persist 1.652
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 1.988
And I take note of which tps features are available 0.174
And I shutdown Tails and wait for the computer to power off 8.288
# 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" 12.553
After features/support/hooks.rb:335 0.134
After features/support/hooks.rb:104 0.006
Tags: @product
2:11.356
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 without a persistent partition and stopped at Tails Greeter's login screen 8.015
And I log in to a new session 13.236
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.967
And I plug USB drive "to_upgrade" 2.356
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.182
Then the running Tails is installed on USB drive "to_upgrade" 15.313
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:335 2.047
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.449
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.846
Then all tps features from the old Tails version are active 1.248
And Tails is running from USB drive "to_upgrade" 0.268
And the boot device has safe access rights 2.805
And the expected persistent files created with the old Tails version are present in the filesystem 1.181
And all persistent directories from the old Tails version have safe access rights 2.039
After features/support/hooks.rb:335 0.810
After features/support/hooks.rb:104 0.032
Tags: @product @automatic_upgrade
3:38.256
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 with a persistent partition enabled and logged in 8.126
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.017
And Tor is ready 13.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.694
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.924
Given I shutdown Tails and wait for the computer to power off 9.620
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.839
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.582
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.304
When the network is plugged 0.017
And Tor is ready 10.070
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.767
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.234
Given I shutdown Tails and wait for the computer to power off 3.991
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.022
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.178
And the file system changes introduced in version 6.3~testoverlayfs are present 0.417
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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.234
When the network is plugged 0.014
And Tor is ready 9.983
Then the Upgrader considers the system as up-to-date 10.627
# 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.802
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.415
After features/support/hooks.rb:335 0.698
After features/support/hooks.rb:104 0.029
Tags: @product @automatic_upgrade
19.762
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 with a persistent partition enabled and logged in 7.427
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.065
After features/support/hooks.rb:335 1.009
After features/support/hooks.rb:104 0.000