Project Number Date
test_Tails_ISO_stable 6410 29 May 2026, 11:37

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:28.667 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:14.415
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.387
When I start Tails from USB drive "old" with network unplugged 56.541
Then the boot device has safe access rights 2.725
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:335 3.680
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.950
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 53.531
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 25.743
And I take note of which tps features are available 0.356
Then a Tails persistence partition exists on USB drive "old" 0.570
And I shutdown Tails and wait for the computer to power off 4.408
After features/support/hooks.rb:335 0.390
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.778
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.685
Then Tails is running from USB drive "old" 0.319
And all tps features are active 1.187
When I write some files expected to persist 1.211
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.304
And all persistent directories from the old Tails version have safe access rights 1.833
And I take note of which tps features are available 0.203
And I shutdown Tails and wait for the computer to power off 4.325
# 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.448
After features/support/hooks.rb:335 0.589
After features/support/hooks.rb:104 0.007
Tags: @product
2:10.577
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.812
And I log in to a new session 13.008
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.684
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.338
Then the running Tails is installed on USB drive "to_upgrade" 15.215
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:335 2.094
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.165
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.029
Then all tps features from the old Tails version are active 1.056
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 2.553
And the expected persistent files created with the old Tails version are present in the filesystem 1.145
And all persistent directories from the old Tails version have safe access rights 1.991
After features/support/hooks.rb:335 0.601
After features/support/hooks.rb:104 0.027
Tags: @product @automatic_upgrade
3:42.571
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.345
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.245
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.408
When the network is plugged 0.018
And Tor is ready 12.647
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.663
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.428
Given I shutdown Tails and wait for the computer to power off 10.748
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.921
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.259
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.253
When the network is plugged 0.017
And Tor is ready 9.777
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.340
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.753
Given I shutdown Tails and wait for the computer to power off 4.049
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.350
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.168
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.039
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.015
And Tor is ready 10.278
Then the Upgrader considers the system as up-to-date 10.521
# 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.358
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:335 0.882
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
21.209
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.703
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
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.018
And Tor is ready 9.611
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.523
After features/support/hooks.rb:335 1.040
After features/support/hooks.rb:104 0.000