Project Number Date
test_Tails_ISO_21643-uefi-db 5 13 Jun 2026, 02:20

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:24.569 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
58.026
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.037
Given a computer 0.118
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 12.620
When I start Tails from USB drive "old" with network unplugged 41.416
Then the boot device has safe access rights 2.188
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.534
After features/support/hooks.rb:108 0.018
Tags: @product
1:30.146
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.115
And I start Tails from USB drive "old" with network unplugged and I login 52.809
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 24.198
And I take note of which tps features are available 4.031
Then a Tails persistence partition exists on USB drive "old" 0.480
And I shutdown Tails and wait for the computer to power off 8.275
After features/support/hooks.rb:339 0.251
After features/support/hooks.rb:108 0.019
Tags: @product
1:29.649
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.123
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.330
Then Tails is running from USB drive "old" 0.213
And all tps features are active 4.596
When I write some files expected to persist 1.248
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.999
And I take note of which tps features are available 3.691
And I shutdown Tails and wait for the computer to power off 4.268
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.756
After features/support/hooks.rb:339 0.181
After features/support/hooks.rb:108 0.019
Tags: @product
2:9.650
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.043
And I log in to a new session 12.561
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.815
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.369
Then the running Tails is installed on USB drive "to_upgrade" 14.383
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 2.145
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.184
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.117
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.321
Then all tps features from the old Tails version are active 0.916
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 2.421
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.926
After features/support/hooks.rb:339 0.596
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:46.907
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.578
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.307
When the network is plugged 0.015
And Tor is ready 12.347
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.568
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.087
Given I shutdown Tails and wait for the computer to power off 7.229
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.170
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.558
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# 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.184
When the network is plugged 0.018
And Tor is ready 9.634
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.866
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.597
Given I shutdown Tails and wait for the computer to power off 8.070
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.792
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.845
And the file system changes introduced in version 6.3~testoverlayfs are present 0.330
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.014
And Tor is ready 10.532
Then the Upgrader considers the system as up-to-date 10.483
# 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 3.821
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 1.005
After features/support/hooks.rb:108 0.034
Tags: @product @automatic_upgrade
20.003
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.852
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.521
After features/support/hooks.rb:339 0.715
After features/support/hooks.rb:108 0.000