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

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 12:29.446 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:11.456
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
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.685
When I start Tails from USB drive "old" with network unplugged 53.174
Then the boot device has safe access rights 2.850
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:335 1.700
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.633
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.012
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 53.954
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 25.055
And I take note of which tps features are available 0.815
Then a Tails persistence partition exists on USB drive "old" 0.576
And I shutdown Tails and wait for the computer to power off 6.796
After features/support/hooks.rb:335 0.223
After features/support/hooks.rb:104 0.008
Tags: @product
1:24.118
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.035
Then Tails is running from USB drive "old" 0.261
And all tps features are active 1.201
When I write some files expected to persist 1.238
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.298
And I take note of which tps features are available 0.207
And I shutdown Tails and wait for the computer to power off 4.164
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.033
After features/support/hooks.rb:335 0.309
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.903
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.361
And I log in to a new session 11.900
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.758
And I plug USB drive "to_upgrade" 2.847
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.711
Then the running Tails is installed on USB drive "to_upgrade" 17.042
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:335 2.367
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.552
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.065
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.365
Then all tps features from the old Tails version are active 1.144
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.323
And the expected persistent files created with the old Tails version are present in the filesystem 1.402
And all persistent directories from the old Tails version have safe access rights 2.006
After features/support/hooks.rb:335 0.737
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
4:36.711
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.497
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.017
And Tor is ready 20.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.370
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.996
Given I shutdown Tails and wait for the computer to power off 20.210
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.314
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.134
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.176
# 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.307
When the network is plugged 0.017
And Tor is ready 21.090
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.357
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.176
Given I shutdown Tails and wait for the computer to power off 12.143
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.846
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.009
And the file system changes introduced in version 6.3~testoverlayfs are present 0.339
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.016
And Tor is ready 23.226
Then the Upgrader considers the system as up-to-date 0.093
# 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.523
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.415
After features/support/hooks.rb:335 0.922
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
27.071
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.814
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 18.540
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.383
After features/support/hooks.rb:335 0.712
After features/support/hooks.rb:104 0.000