Project Number Date
test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry 6 03 May 2026, 23:09

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:12.245 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:14.452
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.088
When I start Tails from USB drive "old" with network unplugged 56.841
Then the boot device has safe access rights 2.707
And Tails is running from USB drive "old" 0.277
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.664
After features/support/hooks.rb:100 0.015
Tags: @product
1:24.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 52.196
Then Tails is running from USB drive "old" 0.213
And I create a persistent partition 23.931
And I take note of which tps features are available 0.636
Then a Tails persistence partition exists on USB drive "old" 0.489
And I shutdown Tails and wait for the computer to power off 6.696
After features/support/hooks.rb:331 0.103
After features/support/hooks.rb:100 0.006
Tags: @product
1:20.355
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.806
Then Tails is running from USB drive "old" 0.247
And all tps features are active 1.134
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 1.837
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 4.193
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.044
After features/support/hooks.rb:331 0.477
After features/support/hooks.rb:100 0.007
Tags: @product
2:7.904
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 7.461
And I log in to a new session 12.066
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.764
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.058
Then the running Tails is installed on USB drive "to_upgrade" 14.060
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 1.936
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.123
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.254
Then all tps features from the old Tails version are active 0.987
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.469
And the expected persistent files created with the old Tails version are present in the filesystem 1.178
And all persistent directories from the old Tails version have safe access rights 1.933
After features/support/hooks.rb:331 0.541
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:33.545
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 with a persistent partition enabled and logged in 8.092
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.325
When the network is plugged 0.017
And Tor is ready 20.905
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.436
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.664
Given I shutdown Tails and wait for the computer to power off 19.865
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.608
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.017
And the file system changes introduced in version 6.2~testoverlayfs are present 0.200
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.152
# 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.232
When the network is plugged 0.015
And Tor is ready 22.916
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.349
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.368
Given I shutdown Tails and wait for the computer to power off 18.440
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.168
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.115
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.013
And Tor is ready 21.424
Then the Upgrader considers the system as up-to-date 0.115
# 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.318
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.385
After features/support/hooks.rb:331 0.890
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
23.651
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 with a persistent partition enabled and logged in 7.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
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.015
And Tor is ready 15.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.366
After features/support/hooks.rb:331 0.592
After features/support/hooks.rb:100 0.000