Project Number Date
test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry 5 02 May 2026, 23:29

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:3.578 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:16.140
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.809
When I start Tails from USB drive "old" with network unplugged 57.827
Then the boot device has safe access rights 2.668
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.240
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 3.514
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.377
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login 59.036
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 24.506
And I take note of which tps features are available 0.695
Then a Tails persistence partition exists on USB drive "old" 0.562
And I shutdown Tails and wait for the computer to power off 8.227
After features/support/hooks.rb:331 0.678
After features/support/hooks.rb:100 0.008
Tags: @product
1:27.449
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.492
Then Tails is running from USB drive "old" 0.281
And all tps features are active 1.281
When I write some files expected to persist 1.409
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 1.980
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 4.079
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.068
After features/support/hooks.rb:331 0.430
After features/support/hooks.rb:100 0.007
Tags: @product
2:17.361
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.147
And I log in to a new session 16.555
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.998
And I plug USB drive "to_upgrade" 2.300
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.650
Then the running Tails is installed on USB drive "to_upgrade" 16.354
And I unplug USB drive "to_upgrade" 0.182
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:331 3.703
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.306
Then all tps features from the old Tails version are active 0.998
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 2.432
And the expected persistent files created with the old Tails version are present in the filesystem 1.074
And all persistent directories from the old Tails version have safe access rights 2.064
After features/support/hooks.rb:331 0.623
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:49.725
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 with a persistent partition enabled and logged in 8.682
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.401
When the network is plugged 0.046
And Tor is ready 27.388
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.434
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.216
Given I shutdown Tails and wait for the computer to power off 21.477
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.439
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.224
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
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.140
# 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.196
When the network is plugged 0.017
And Tor is ready 21.236
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.534
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.793
Given I shutdown Tails and wait for the computer to power off 17.625
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.884
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.392
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.098
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.020
And Tor is ready 20.790
Then the Upgrader considers the system as up-to-date 0.084
# 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.335
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:331 0.958
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
27.350
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 7.545
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 18.958
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.410
After features/support/hooks.rb:331 0.917
After features/support/hooks.rb:100 0.000