Project Number Date
test_Tails_ISO_21643-uefi-db 4 12 Jun 2026, 02:12

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:46.946 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:10.748
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.016
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 12.994
When I start Tails from USB drive "old" with network unplugged 53.546
Then the boot device has safe access rights 2.440
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 3.884
After features/support/hooks.rb:108 0.014
Tags: @product
1:30.682
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.119
And I start Tails from USB drive "old" with network unplugged and I login 52.720
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 24.628
And I take note of which tps features are available 4.147
Then a Tails persistence partition exists on USB drive "old" 0.577
And I shutdown Tails and wait for the computer to power off 8.225
After features/support/hooks.rb:339 0.181
After features/support/hooks.rb:108 0.015
Tags: @product
1:35.605
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.150
Then Tails is running from USB drive "old" 0.213
And all tps features are active 4.879
When I write some files expected to persist 1.244
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.935
And I take note of which tps features are available 3.758
And I shutdown Tails and wait for the computer to power off 7.969
# 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:339 0.287
After features/support/hooks.rb:108 0.015
Tags: @product
2:9.039
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.617
And I log in to a new session 12.774
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.696
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.133
Then the running Tails is installed on USB drive "to_upgrade" 14.346
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 0.701
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.961
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.435
Then all tps features from the old Tails version are active 0.932
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 2.315
And the expected persistent files created with the old Tails version are present in the filesystem 1.078
And all persistent directories from the old Tails version have safe access rights 1.748
After features/support/hooks.rb:339 0.732
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
3:51.513
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.189
And no SquashFS delta is installed 0.043
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.404
When the network is plugged 0.015
And Tor is ready 13.040
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.522
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.657
Given I shutdown Tails and wait for the computer to power off 9.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.712
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.622
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
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.127
# 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.191
When the network is plugged 0.015
And Tor is ready 9.557
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.776
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.476
Given I shutdown Tails and wait for the computer to power off 8.003
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.861
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.551
And the file system changes introduced in version 6.3~testoverlayfs are present 0.364
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.017
And Tor is ready 11.233
Then the Upgrader considers the system as up-to-date 10.486
# 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.371
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.376
After features/support/hooks.rb:339 0.940
After features/support/hooks.rb:108 0.061
Tags: @product @automatic_upgrade
19.395
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.027
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.599
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.012
And Tor is ready 9.541
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.968
After features/support/hooks.rb:339 0.784
After features/support/hooks.rb:108 0.000