Project Number Date
test_Tails_ISO_stable 6716 01 Oct 2026, 17:15

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 12:11.680 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:20.317
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.033
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 13.882
When I start Tails from USB drive "old" with network unplugged 1:2.140
Then the boot device has safe access rights 2.455
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 3.739
After features/support/hooks.rb:108 0.022
Tags: @product
1:27.857
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 50.895
Then Tails is running from USB drive "old" 0.187
And I create a persistent partition 25.432
And I take note of which tps features are available 6.594
Then a Tails persistence partition exists on USB drive "old" 0.489
And I shutdown Tails and wait for the computer to power off 4.183
After features/support/hooks.rb:339 0.492
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.650
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.408
Then Tails is running from USB drive "old" 0.249
And all tps features are active 8.137
When I write some files expected to persist 1.198
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.142
And all persistence configuration files have safe access rights 0.250
And all persistent directories from the old Tails version have safe access rights 1.814
And I take note of which tps features are available 6.951
And I shutdown Tails and wait for the computer to power off 4.367
# 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.042
After features/support/hooks.rb:339 0.176
After features/support/hooks.rb:108 0.008
Tags: @product
2:16.043
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 without a persistent partition and stopped at Tails Greeter's login screen 9.178
And I log in to a new session 12.584
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.650
And I plug USB drive "to_upgrade" 1.815
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.757
Then the running Tails is installed on USB drive "to_upgrade" 19.815
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 3.592
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.474
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.354
Then all tps features from the old Tails version are active 1.292
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 2.806
And the expected persistent files created with the old Tails version are present in the filesystem 1.030
And all persistent directories from the old Tails version have safe access rights 1.559
After features/support/hooks.rb:339 2.124
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:50.983
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.400
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.548
When the network is plugged 1.227
And Tor is ready 11.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.847
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.924
Given I shutdown Tails and wait for the computer to power off 5.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.121
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 9.302
And the file system changes introduced in version 6.2~testoverlayfs are present 0.181
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.096
# 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.172
When the network is plugged 0.027
And Tor is ready 11.008
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.441
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.189
Given I shutdown Tails and wait for the computer to power off 4.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.583
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 10.283
And the file system changes introduced in version 6.3~testoverlayfs are present 0.301
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.162
When the network is plugged 0.025
And Tor is ready 11.108
Then the Upgrader considers the system as up-to-date 0.097
# 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.816
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.427
After features/support/hooks.rb:339 0.974
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.354
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.537
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
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.052
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.142
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.346
After features/support/hooks.rb:339 0.841
After features/support/hooks.rb:108 0.000