Project Number Date
test_Tails_ISO_stable 6437 10 Jun 2026, 11:20

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:52.835 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.361
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.061
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" 13.066
When I start Tails from USB drive "old" with network unplugged 46.051
Then the boot device has safe access rights 2.486
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:335 3.741
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.598
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 51.985
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 23.648
And I take note of which tps features are available 0.325
Then a Tails persistence partition exists on USB drive "old" 0.496
And I shutdown Tails and wait for the computer to power off 7.850
After features/support/hooks.rb:335 0.267
After features/support/hooks.rb:104 0.006
Tags: @product
1:21.002
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.164
Then Tails is running from USB drive "old" 0.255
And all tps features are active 1.079
When I write some files expected to persist 1.210
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
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.895
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 3.993
# 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.650
After features/support/hooks.rb:335 0.287
After features/support/hooks.rb:104 0.006
Tags: @product
2:8.916
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.297
And I log in to a new session 11.693
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.672
And I plug USB drive "to_upgrade" 2.256
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.785
Then the running Tails is installed on USB drive "to_upgrade" 14.924
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:335 1.889
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.546
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.129
Then all tps features from the old Tails version are active 0.923
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.316
And the expected persistent files created with the old Tails version are present in the filesystem 1.122
And all persistent directories from the old Tails version have safe access rights 1.793
After features/support/hooks.rb:335 0.755
After features/support/hooks.rb:104 0.006
3:30.259
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.042
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
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.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.016
And Tor is ready 12.699
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.785
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.102
Given I shutdown Tails and wait for the computer to power off 9.355
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.477
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.082
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.180
When the network is plugged 0.013
And Tor is ready 10.685
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.663
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.587
Given I shutdown Tails and wait for the computer to power off 8.127
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.589
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.124
And the file system changes introduced in version 6.3~testoverlayfs are present 0.419
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.017
And Tor is ready 9.531
Then the Upgrader considers the system as up-to-date 10.536
# 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.094
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.339
After features/support/hooks.rb:335 0.650
After features/support/hooks.rb:104 0.010
19.151
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 6.986
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
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.058
And Tor is ready 9.474
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.327
After features/support/hooks.rb:335 0.603
After features/support/hooks.rb:104 0.000