Project Number Date
test_Tails_ISO_21529-test-suite-vs-secure-boot-key-expiry 9 05 May 2026, 23:11

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 11:57.960 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:2.009
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 12.950
When I start Tails from USB drive "old" with network unplugged 44.792
Then the boot device has safe access rights 2.516
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.584
After features/support/hooks.rb:100 0.067
Tags: @product
1:26.558
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 53.901
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 23.198
And I take note of which tps features are available 0.657
Then a Tails persistence partition exists on USB drive "old" 0.584
And I shutdown Tails and wait for the computer to power off 7.896
After features/support/hooks.rb:331 0.329
After features/support/hooks.rb:100 0.007
Tags: @product
1:21.038
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.186
Then Tails is running from USB drive "old" 0.256
And all tps features are active 1.160
When I write some files expected to persist 1.262
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.003
And I take note of which tps features are available 0.163
And I shutdown Tails and wait for the computer to power off 4.323
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.009
After features/support/hooks.rb:331 0.299
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.860
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.737
And I log in to a new session 11.560
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.819
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.647
Then the running Tails is installed on USB drive "to_upgrade" 16.604
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 2.190
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.355
Then all tps features from the old Tails version are active 0.891
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.339
And the expected persistent files created with the old Tails version are present in the filesystem 1.026
And all persistent directories from the old Tails version have safe access rights 1.836
After features/support/hooks.rb:331 0.977
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:24.907
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.305
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
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.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.020
And Tor is ready 19.558
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 5.349
Given I shutdown Tails and wait for the computer to power off 14.785
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.327
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.026
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
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.135
# 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.189
When the network is plugged 0.018
And Tor is ready 20.113
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.471
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.707
Given I shutdown Tails and wait for the computer to power off 17.210
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.592
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.118
And the file system changes introduced in version 6.3~testoverlayfs are present 0.382
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.015
And Tor is ready 21.820
Then the Upgrader considers the system as up-to-date 0.106
# 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.284
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.362
After features/support/hooks.rb:331 0.998
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
25.844
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.462
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
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 17.715
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.349
After features/support/hooks.rb:331 0.894
After features/support/hooks.rb:100 0.000