Project Number Date
test_Tails_ISO_stable 6374 14 May 2026, 11:21

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:8.549 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.102
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.071
When I start Tails from USB drive "old" with network unplugged 40.562
Then the boot device has safe access rights 2.754
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:335 3.469
After features/support/hooks.rb:104 0.023
Tags: @product
1:28.006
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 53.502
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 24.947
And I take note of which tps features are available 0.373
Then a Tails persistence partition exists on USB drive "old" 0.659
And I shutdown Tails and wait for the computer to power off 8.214
After features/support/hooks.rb:335 0.391
After features/support/hooks.rb:104 0.008
Tags: @product
1:22.164
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.710
Then Tails is running from USB drive "old" 0.216
And all tps features are active 1.060
When I write some files expected to persist 1.222
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 1.887
And I take note of which tps features are available 0.188
And I shutdown Tails and wait for the computer to power off 3.990
# 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.294
After features/support/hooks.rb:335 0.206
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.866
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.626
And I log in to a new session 12.261
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.704
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.405
Then the running Tails is installed on USB drive "to_upgrade" 15.290
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.166
After features/support/hooks.rb:335 2.320
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.418
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.402
Then all tps features from the old Tails version are active 0.989
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.726
And the expected persistent files created with the old Tails version are present in the filesystem 1.082
And all persistent directories from the old Tails version have safe access rights 1.924
After features/support/hooks.rb:335 0.809
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
3:41.337
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.504
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.422
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.017
And Tor is ready 13.693
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.598
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.264
Given I shutdown Tails and wait for the computer to power off 9.414
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.611
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.228
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
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.135
# 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.016
And Tor is ready 9.928
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.031
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.037
Given I shutdown Tails and wait for the computer to power off 8.008
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.797
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.106
And the file system changes introduced in version 6.3~testoverlayfs are present 0.341
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.017
And Tor is ready 10.149
Then the Upgrader considers the system as up-to-date 10.545
# 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.250
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.451
After features/support/hooks.rb:335 0.586
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
20.653
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.604
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.096
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.356
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.268
After features/support/hooks.rb:335 0.556
After features/support/hooks.rb:104 0.000