Project Number Date
test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry 10 06 May 2026, 23:08

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:13.884 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.093
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 13.109
When I start Tails from USB drive "old" with network unplugged 57.664
Then the boot device has safe access rights 2.572
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.471
After features/support/hooks.rb:100 0.023
Tags: @product
1:24.913
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 51.711
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 23.515
And I take note of which tps features are available 0.617
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 8.191
After features/support/hooks.rb:331 0.403
After features/support/hooks.rb:100 0.007
Tags: @product
1:21.452
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.068
Then Tails is running from USB drive "old" 0.260
And all tps features are active 1.258
When I write some files expected to persist 1.222
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 1.902
And I take note of which tps features are available 0.161
And I shutdown Tails and wait for the computer to power off 4.001
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.922
After features/support/hooks.rb:331 0.370
After features/support/hooks.rb:100 0.008
Tags: @product
2:9.039
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.797
And I log in to a new session 11.662
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.735
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.137
Then the running Tails is installed on USB drive "to_upgrade" 15.205
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:331 2.100
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.556
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.784
Then all tps features from the old Tails version are active 0.942
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.526
And the expected persistent files created with the old Tails version are present in the filesystem 1.121
And all persistent directories from the old Tails version have safe access rights 1.902
After features/support/hooks.rb:331 0.740
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:32.483
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.290
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.322
When the network is plugged 0.015
And Tor is ready 22.011
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.366
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.147
Given I shutdown Tails and wait for the computer to power off 19.938
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.819
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.050
And the file system changes introduced in version 6.2~testoverlayfs are present 0.246
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.144
# 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.231
When the network is plugged 0.013
And Tor is ready 21.551
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.880
Given I shutdown Tails and wait for the computer to power off 17.095
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.218
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.131
And the file system changes introduced in version 6.3~testoverlayfs are present 0.337
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.016
And Tor is ready 20.545
Then the Upgrader considers the system as up-to-date 0.146
# 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.160
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.411
After features/support/hooks.rb:331 0.929
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
24.345
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.191
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.045
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.013
And Tor is ready 16.447
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.351
After features/support/hooks.rb:331 0.852
After features/support/hooks.rb:100 0.000