Project Number Date
test_Tails_ISO_stable 6381 16 May 2026, 11:22

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:59.816 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
59.972
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.338
When I start Tails from USB drive "old" with network unplugged 42.301
Then the boot device has safe access rights 2.536
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:335 1.314
After features/support/hooks.rb:104 0.005
Tags: @product
1:22.847
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 50.193
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 23.510
And I take note of which tps features are available 0.364
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 7.924
After features/support/hooks.rb:335 0.476
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.547
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.742
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.121
When I write some files expected to persist 1.195
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.970
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 7.981
# 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.654
After features/support/hooks.rb:335 0.268
After features/support/hooks.rb:104 0.005
Tags: @product
2:8.441
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 7.478
And I log in to a new session 11.945
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.706
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.724
Then the running Tails is installed on USB drive "to_upgrade" 15.094
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:335 1.821
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.835
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.059
Then all tps features from the old Tails version are active 0.925
And Tails is running from USB drive "to_upgrade" 0.268
And the boot device has safe access rights 2.444
And the expected persistent files created with the old Tails version are present in the filesystem 1.137
And all persistent directories from the old Tails version have safe access rights 1.945
After features/support/hooks.rb:335 0.912
After features/support/hooks.rb:104 0.005
Tags: @product @automatic_upgrade
3:38.026
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.246
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.176
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.346
When the network is plugged 0.017
And Tor is ready 12.139
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.779
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.635
Given I shutdown Tails and wait for the computer to power off 9.217
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.305
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.028
And the file system changes introduced in version 6.2~testoverlayfs are present 0.227
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.191
When the network is plugged 0.014
And Tor is ready 9.608
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.978
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.958
Given I shutdown Tails and wait for the computer to power off 8.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.561
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.123
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.056
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.019
And Tor is ready 11.102
Then the Upgrader considers the system as up-to-date 10.514
# 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.838
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.409
After features/support/hooks.rb:335 0.875
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.144
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.485
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.038
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.932
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.368
After features/support/hooks.rb:335 0.586
After features/support/hooks.rb:104 0.000