Project Number Date
test_Tails_ISO_stable 6736 12 Oct 2026, 11:34

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.211 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:14.930
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.857
When I start Tails from USB drive "old" with network unplugged 56.975
Then the boot device has safe access rights 2.295
And Tails is running from USB drive "old" 0.181
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.607
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.110
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 49.174
Then Tails is running from USB drive "old" 0.215
And I create a persistent partition 24.722
And I take note of which tps features are available 6.653
Then a Tails persistence partition exists on USB drive "old" 0.537
And I shutdown Tails and wait for the computer to power off 2.711
After features/support/hooks.rb:339 0.224
After features/support/hooks.rb:108 0.007
Tags: @product
1:33.725
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.079
Then Tails is running from USB drive "old" 0.215
And all tps features are active 6.940
When I write some files expected to persist 1.253
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.145
And all persistence configuration files have safe access rights 0.314
And all persistent directories from the old Tails version have safe access rights 1.811
And I take note of which tps features are available 6.066
And I shutdown Tails and wait for the computer to power off 2.582
# 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.218
After features/support/hooks.rb:339 0.075
After features/support/hooks.rb:108 0.005
Tags: @product
2:18.882
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.718
And I log in to a new session 12.691
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.993
And I plug USB drive "to_upgrade" 2.550
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.574
Then the running Tails is installed on USB drive "to_upgrade" 20.018
And I unplug USB drive "to_upgrade" 0.176
And I unplug USB drive "__internal" 0.159
After features/support/hooks.rb:339 1.875
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.821
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.317
Then all tps features from the old Tails version are active 1.223
And Tails is running from USB drive "to_upgrade" 0.184
And the boot device has safe access rights 2.360
And the expected persistent files created with the old Tails version are present in the filesystem 0.984
And all persistent directories from the old Tails version have safe access rights 1.662
After features/support/hooks.rb:339 0.833
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:47.215
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 9.155
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.029
And Tor is ready 13.066
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.234
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.060
Given I shutdown Tails and wait for the computer to power off 5.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.313
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.298
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.213
When the network is plugged 0.025
And Tor is ready 10.231
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.671
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.860
Given I shutdown Tails and wait for the computer to power off 2.568
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.953
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 10.807
And the file system changes introduced in version 6.3~testoverlayfs are present 0.370
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.025
And Tor is ready 11.385
Then the Upgrader considers the system as up-to-date 0.085
# 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.222
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.393
After features/support/hooks.rb:339 0.679
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
19.525
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 with a persistent partition enabled and logged in 8.431
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.068
And Tor is ready 10.226
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.466
After features/support/hooks.rb:339 0.634
After features/support/hooks.rb:108 0.000