Project Number Date
test_Tails_ISO_stable 6723 05 Oct 2026, 12: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:59.663 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:10.220
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.896
When I start Tails from USB drive "old" with network unplugged 52.051
Then the boot device has safe access rights 2.605
And Tails is running from USB drive "old" 0.169
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.455
After features/support/hooks.rb:108 0.007
Tags: @product
1:28.969
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 48.877
Then Tails is running from USB drive "old" 0.788
And I create a persistent partition 24.049
And I take note of which tps features are available 10.650
Then a Tails persistence partition exists on USB drive "old" 0.616
And I shutdown Tails and wait for the computer to power off 3.889
After features/support/hooks.rb:339 0.492
After features/support/hooks.rb:108 0.005
Tags: @product
1:46.437
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 1.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.084
Then Tails is running from USB drive "old" 0.211
And all tps features are active 7.968
When I write some files expected to persist 1.238
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.253
And all persistent directories from the old Tails version have safe access rights 1.779
And I take note of which tps features are available 11.019
And I shutdown Tails and wait for the computer to power off 4.474
# 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" 14.077
After features/support/hooks.rb:339 0.379
After features/support/hooks.rb:108 0.008
Tags: @product
2:17.189
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.042
And I log in to a new session 11.318
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.683
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.258
Then the running Tails is installed on USB drive "to_upgrade" 19.217
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:339 0.610
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.330
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.680
Then all tps features from the old Tails version are active 1.070
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.307
And the expected persistent files created with the old Tails version are present in the filesystem 1.028
And all persistent directories from the old Tails version have safe access rights 1.937
After features/support/hooks.rb:339 0.938
After features/support/hooks.rb:108 0.024
Tags: @product @automatic_upgrade
3:44.311
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.654
And no SquashFS delta is installed 0.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.030
And Tor is ready 13.408
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.720
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.931
Given I shutdown Tails and wait for the computer to power off 5.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.146
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 10.912
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.156
When the network is plugged 0.024
And Tor is ready 11.329
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.935
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.670
Given I shutdown Tails and wait for the computer to power off 3.949
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.749
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 9.190
And the file system changes introduced in version 6.3~testoverlayfs are present 0.331
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.032
And Tor is ready 10.822
Then the Upgrader considers the system as up-to-date 0.104
# 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.764
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.338
After features/support/hooks.rb:339 1.028
After features/support/hooks.rb:108 0.052
Tags: @product @automatic_upgrade
21.203
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.677
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 9.309
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.822
After features/support/hooks.rb:339 0.999
After features/support/hooks.rb:108 0.000