Project Number Date
test_Tails_ISO_stable 6411 30 May 2026, 11:24

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:0.404 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:3.736
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.056
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" 12.886
When I start Tails from USB drive "old" with network unplugged 46.677
Then the boot device has safe access rights 2.479
And Tails is running from USB drive "old" 0.199
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:335 3.823
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.650
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.018
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 51.199
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 24.057
And I take note of which tps features are available 0.325
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 8.251
After features/support/hooks.rb:335 0.251
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.563
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.346
Then Tails is running from USB drive "old" 0.241
And all tps features are active 1.097
When I write some files expected to persist 1.279
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.289
And all persistent directories from the old Tails version have safe access rights 1.756
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 8.190
# 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.991
After features/support/hooks.rb:335 0.264
After features/support/hooks.rb:104 0.007
Tags: @product
2:9.607
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.003
And I log in to a new session 13.058
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.710
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.270
Then the running Tails is installed on USB drive "to_upgrade" 14.032
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:335 3.722
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.298
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.510
Then all tps features from the old Tails version are active 1.078
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.549
And the expected persistent files created with the old Tails version are present in the filesystem 1.071
And all persistent directories from the old Tails version have safe access rights 1.817
After features/support/hooks.rb:335 0.934
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:32.139
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.043
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.197
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.366
When the network is plugged 0.014
And Tor is ready 13.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.934
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.118
Given I shutdown Tails and wait for the computer to power off 9.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.717
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.111
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.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.230
When the network is plugged 0.018
And Tor is ready 10.028
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.257
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.657
Given I shutdown Tails and wait for the computer to power off 3.960
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.333
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.091
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.016
And Tor is ready 10.574
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 3.736
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.366
After features/support/hooks.rb:335 0.919
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.408
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.335
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.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.014
And Tor is ready 9.353
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.369
After features/support/hooks.rb:335 0.841
After features/support/hooks.rb:104 0.000