Project Number Date
test_Tails_ISO_stable 6739 12 Oct 2026, 13:09

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:51.212 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:15.973
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.131
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.380
When I start Tails from USB drive "old" with network unplugged 57.684
Then the boot device has safe access rights 2.188
And Tails is running from USB drive "old" 0.167
And there is no persistence partition on USB drive "old" 0.031
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 1.147
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.807
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login 49.183
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 23.290
And I take note of which tps features are available 7.013
Then a Tails persistence partition exists on USB drive "old" 0.615
And I shutdown Tails and wait for the computer to power off 4.351
After features/support/hooks.rb:339 0.518
After features/support/hooks.rb:108 0.006
Tags: @product
1:42.010
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.778
Then Tails is running from USB drive "old" 0.308
And all tps features are active 7.752
When I write some files expected to persist 1.361
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.337
And all persistent directories from the old Tails version have safe access rights 1.775
And I take note of which tps features are available 7.231
And I shutdown Tails and wait for the computer to power off 4.092
# 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" 13.112
After features/support/hooks.rb:339 0.352
After features/support/hooks.rb:108 0.009
Tags: @product
2:16.039
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.967
And I log in to a new session 13.591
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.821
And I plug USB drive "to_upgrade" 2.250
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.097
Then the running Tails is installed on USB drive "to_upgrade" 18.063
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 1.938
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.872
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.702
Then all tps features from the old Tails version are active 1.393
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.705
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.694
After features/support/hooks.rb:339 0.790
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:40.771
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.866
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.325
When the network is plugged 0.026
And Tor is ready 11.971
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.088
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.076
Given I shutdown Tails and wait for the computer to power off 5.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.418
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 8.571
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.210
When the network is plugged 0.026
And Tor is ready 10.406
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.389
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.034
Given I shutdown Tails and wait for the computer to power off 4.077
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.821
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.358
And the file system changes introduced in version 6.3~testoverlayfs are present 0.381
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.177
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.091
And Tor is ready 10.538
Then the Upgrader considers the system as up-to-date 0.122
# 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.416
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.353
After features/support/hooks.rb:339 0.735
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.737
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.425
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
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.045
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 9.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.955
After features/support/hooks.rb:339 0.954
After features/support/hooks.rb:108 0.000