Project Number Date
test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry 7 04 May 2026, 16:02

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 13:23.044 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.900
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 15.576
When I start Tails from USB drive "old" with network unplugged 1:0.497
Then the boot device has safe access rights 3.002
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 4.018
After features/support/hooks.rb:100 0.010
Tags: @product
1:36.893
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login 1:1.609
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 24.854
And I take note of which tps features are available 0.860
Then a Tails persistence partition exists on USB drive "old" 0.673
And I shutdown Tails and wait for the computer to power off 8.539
After features/support/hooks.rb:331 0.508
After features/support/hooks.rb:100 0.008
Tags: @product
1:34.658
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.640
Then Tails is running from USB drive "old" 0.354
And all tps features are active 1.821
When I write some files expected to persist 1.715
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.267
And all persistence configuration files have safe access rights 0.593
And all persistent directories from the old Tails version have safe access rights 1.997
And I take note of which tps features are available 0.193
And I shutdown Tails and wait for the computer to power off 8.080
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.936
After features/support/hooks.rb:331 0.167
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.165
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.393
And I log in to a new session 13.803
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.939
And I plug USB drive "to_upgrade" 2.294
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.947
Then the running Tails is installed on USB drive "to_upgrade" 17.455
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:331 2.086
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.107
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.950
Then all tps features from the old Tails version are active 1.119
And Tails is running from USB drive "to_upgrade" 0.492
And the boot device has safe access rights 2.990
And the expected persistent files created with the old Tails version are present in the filesystem 1.369
And all persistent directories from the old Tails version have safe access rights 2.102
After features/support/hooks.rb:331 0.589
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:51.578
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.514
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.021
And Tor is ready 21.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.369
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.994
Given I shutdown Tails and wait for the computer to power off 21.121
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.849
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.280
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.260
When the network is plugged 0.015
And Tor is ready 20.595
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.396
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.543
Given I shutdown Tails and wait for the computer to power off 18.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.968
Then Tails is running version 6.3~testoverlayfs 0.041
And all tps features are active 1.407
And the file system changes introduced in version 6.3~testoverlayfs are present 0.358
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.013
And Tor is ready 22.097
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 4.843
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.401
After features/support/hooks.rb:331 1.121
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
27.740
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.175
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.681
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.411
After features/support/hooks.rb:331 1.063
After features/support/hooks.rb:100 0.000