Project Number Date
test_Tails_ISO_stable 6748 14 Oct 2026, 11:37

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:36.884 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
56.369
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.138
And I create a 7200 MiB disk named "old" 0.034
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 13.086
When I start Tails from USB drive "old" with network unplugged 39.659
Then the boot device has safe access rights 1.813
And Tails is running from USB drive "old" 0.190
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.144
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.702
After features/support/hooks.rb:108 0.028
Tags: @product
1:18.053
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.130
And I start Tails from USB drive "old" with network unplugged and I login 45.550
Then Tails is running from USB drive "old" 0.167
And I create a persistent partition 21.988
And I take note of which tps features are available 5.830
Then a Tails persistence partition exists on USB drive "old" 0.437
And I shutdown Tails and wait for the computer to power off 3.949
After features/support/hooks.rb:339 0.249
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.114
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.448
Then Tails is running from USB drive "old" 0.196
And all tps features are active 6.851
When I write some files expected to persist 1.053
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.246
And all persistent directories from the old Tails version have safe access rights 1.400
And I take note of which tps features are available 5.793
And I shutdown Tails and wait for the computer to power off 2.516
# 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.346
After features/support/hooks.rb:339 0.155
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.626
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 8.093
And I log in to a new session 11.237
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.633
And I plug USB drive "to_upgrade" 2.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.536
Then the running Tails is installed on USB drive "to_upgrade" 17.687
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 0.600
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.897
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.965
Then all tps features from the old Tails version are active 1.018
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 1.930
And the expected persistent files created with the old Tails version are present in the filesystem 1.100
And all persistent directories from the old Tails version have safe access rights 1.590
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.007
3:20.693
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.103
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.172
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.026
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.165
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.292
When the network is plugged 0.032
And Tor is ready 12.907
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.296
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.415
Given I shutdown Tails and wait for the computer to power off 6.381
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.413
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 7.407
And the file system changes introduced in version 6.2~testoverlayfs are present 0.178
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.073
# 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.163
When the network is plugged 0.044
And Tor is ready 10.126
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.862
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.408
Given I shutdown Tails and wait for the computer to power off 2.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.401
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.494
And the file system changes introduced in version 6.3~testoverlayfs are present 0.287
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.091
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.165
When the network is plugged 0.024
And Tor is ready 9.932
Then the Upgrader considers the system as up-to-date 0.164
# 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.524
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.275
After features/support/hooks.rb:339 0.642
After features/support/hooks.rb:108 0.011
18.129
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 7.638
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.025
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 9.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.800
After features/support/hooks.rb:339 0.550
After features/support/hooks.rb:108 0.000