Project Number Date
test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry 4 01 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:52.949 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.167
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 12.861
When I start Tails from USB drive "old" with network unplugged 57.832
Then the boot device has safe access rights 2.699
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:331 1.532
After features/support/hooks.rb:100 0.006
Tags: @product
1:21.915
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 52.264
Then Tails is running from USB drive "old" 0.214
And I create a persistent partition 24.238
And I take note of which tps features are available 0.600
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 4.023
After features/support/hooks.rb:331 0.466
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.458
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 59.704
Then Tails is running from USB drive "old" 0.242
And all tps features are active 1.079
When I write some files expected to persist 1.167
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 1.841
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 7.797
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.786
After features/support/hooks.rb:331 0.394
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.437
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.732
And I log in to a new session 12.825
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.786
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.927
Then the running Tails is installed on USB drive "to_upgrade" 14.664
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 3.660
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.257
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.507
Then all tps features from the old Tails version are active 0.971
And Tails is running from USB drive "to_upgrade" 0.299
And the boot device has safe access rights 2.370
And the expected persistent files created with the old Tails version are present in the filesystem 1.222
And all persistent directories from the old Tails version have safe access rights 1.838
After features/support/hooks.rb:331 0.964
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:52.734
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.831
And no SquashFS delta is installed 0.074
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.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.013
And Tor is ready 34.460
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.655
Given I shutdown Tails and wait for the computer to power off 5.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.483
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.070
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.197
When the network is plugged 0.015
And Tor is ready 20.659
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.378
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.015
Given I shutdown Tails and wait for the computer to power off 18.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.465
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.071
And the file system changes introduced in version 6.3~testoverlayfs are present 0.321
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.192
When the network is plugged 0.013
And Tor is ready 20.809
Then the Upgrader considers the system as up-to-date 0.097
# 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.673
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:331 0.697
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
41.979
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.374
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
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.042
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 33.920
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.355
After features/support/hooks.rb:331 0.763
After features/support/hooks.rb:100 0.000