Project Number Date
test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry 11 07 May 2026, 12:23

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:50.158 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:18.620
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.014
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.116
When I start Tails from USB drive "old" with network unplugged 59.546
Then the boot device has safe access rights 2.988
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:335 3.960
After features/support/hooks.rb:104 0.027
Tags: @product
1:35.001
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.010
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login 59.746
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 25.007
And I take note of which tps features are available 0.849
Then a Tails persistence partition exists on USB drive "old" 0.629
And I shutdown Tails and wait for the computer to power off 8.384
After features/support/hooks.rb:335 0.419
After features/support/hooks.rb:104 0.010
Tags: @product
1:35.526
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.296
Then Tails is running from USB drive "old" 0.272
And all tps features are active 1.312
When I write some files expected to persist 1.382
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.473
And all persistent directories from the old Tails version have safe access rights 2.021
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 7.042
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.257
After features/support/hooks.rb:335 0.306
After features/support/hooks.rb:104 0.009
Tags: @product
2:17.644
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.679
And I log in to a new session 14.046
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.862
And I plug USB drive "to_upgrade" 2.332
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.803
Then the running Tails is installed on USB drive "to_upgrade" 18.632
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:335 0.732
After features/support/hooks.rb:104 0.000
Tags: @product
1:20.359
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.136
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.664
Then all tps features from the old Tails version are active 1.052
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 2.828
And the expected persistent files created with the old Tails version are present in the filesystem 1.280
And all persistent directories from the old Tails version have safe access rights 2.045
After features/support/hooks.rb:335 0.928
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
5:15.336
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.732
And no SquashFS delta is installed 0.139
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
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.537
When the network is plugged 0.025
And Tor is ready 23.026
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.522
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.385
Given I shutdown Tails and wait for the computer to power off 19.406
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.751
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.179
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.207
When the network is plugged 0.021
And Tor is ready 41.257
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.448
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.286
Given I shutdown Tails and wait for the computer to power off 18.048
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.833
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.629
And the file system changes introduced in version 6.3~testoverlayfs are present 0.755
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.038
And Tor is ready 22.641
Then the Upgrader considers the system as up-to-date 0.128
# 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 5.373
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:335 0.705
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
27.670
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.617
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.298
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.387
After features/support/hooks.rb:335 0.513
After features/support/hooks.rb:104 0.000