Project Number Date
test_Tails_ISO_21643-uefi-db 2 10 Jun 2026, 01:59

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:14.838 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.806
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 12.912
When I start Tails from USB drive "old" with network unplugged 57.684
Then the boot device has safe access rights 2.486
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:335 1.431
After features/support/hooks.rb:104 0.036
Tags: @product
1:26.435
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 52.902
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 24.569
And I take note of which tps features are available 0.328
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 7.842
After features/support/hooks.rb:335 0.451
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.188
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.392
Then Tails is running from USB drive "old" 0.236
And all tps features are active 1.102
When I write some files expected to persist 1.255
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 1.814
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 7.825
# 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.916
After features/support/hooks.rb:335 0.150
After features/support/hooks.rb:104 0.008
Tags: @product
2:10.377
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 8.158
And I log in to a new session 12.801
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.711
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.315
Then the running Tails is installed on USB drive "to_upgrade" 14.888
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:335 2.058
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.393
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.642
Then all tps features from the old Tails version are active 0.982
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.530
And the expected persistent files created with the old Tails version are present in the filesystem 1.098
And all persistent directories from the old Tails version have safe access rights 1.833
After features/support/hooks.rb:335 0.840
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
3:32.580
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.908
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.184
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.016
And Tor is ready 12.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.721
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.497
Given I shutdown Tails and wait for the computer to power off 7.007
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.600
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.122
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.210
When the network is plugged 0.014
And Tor is ready 10.543
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.112
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.842
Given I shutdown Tails and wait for the computer to power off 7.984
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.887
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.419
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.015
And Tor is ready 10.864
Then the Upgrader considers the system as up-to-date 10.570
# 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.127
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.379
After features/support/hooks.rb:335 0.829
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
19.057
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.487
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
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.040
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.469
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.804
After features/support/hooks.rb:335 0.677
After features/support/hooks.rb:104 0.000