Project Number Date
test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry 1 28 Apr 2026, 23:12

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:4.226 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.220
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.677
When I start Tails from USB drive "old" with network unplugged 56.678
Then the boot device has safe access rights 3.047
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.260
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.485
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.791
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 53.715
Then Tails is running from USB drive "old" 0.289
And I create a persistent partition 23.989
And I take note of which tps features are available 0.779
Then a Tails persistence partition exists on USB drive "old" 0.619
And I shutdown Tails and wait for the computer to power off 8.294
After features/support/hooks.rb:331 0.626
After features/support/hooks.rb:100 0.009
Tags: @product
1:29.873
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.685
Then Tails is running from USB drive "old" 0.400
And all tps features are active 1.304
When I write some files expected to persist 1.356
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 2.068
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 7.908
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.339
After features/support/hooks.rb:331 0.509
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.415
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.267
And I log in to a new session 14.029
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.723
And I plug USB drive "to_upgrade" 2.270
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.034
Then the running Tails is installed on USB drive "to_upgrade" 15.795
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:331 2.150
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.045
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.811
Then all tps features from the old Tails version are active 1.232
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 2.586
And the expected persistent files created with the old Tails version are present in the filesystem 1.105
And all persistent directories from the old Tails version have safe access rights 1.929
After features/support/hooks.rb:331 0.737
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:37.631
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.857
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.323
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.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.038
And Tor is ready 21.194
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.493
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.370
Given I shutdown Tails and wait for the computer to power off 19.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.662
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.129
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.166
# 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.279
When the network is plugged 0.018
And Tor is ready 20.872
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.494
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.219
Given I shutdown Tails and wait for the computer to power off 17.323
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.518
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.073
And the file system changes introduced in version 6.3~testoverlayfs are present 0.393
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.015
And Tor is ready 21.995
Then the Upgrader considers the system as up-to-date 0.123
# 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.177
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.349
After features/support/hooks.rb:331 0.893
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
49.247
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.600
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
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.017
And Tor is ready 40.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.407
After features/support/hooks.rb:331 1.249
After features/support/hooks.rb:100 0.000