Project Number Date
test_Tails_ISO_21565-flatpak-safe 81 08 Oct 2026, 18:00

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:16.923 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:3.178
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.374
When I start Tails from USB drive "old" with network unplugged 45.766
Then the boot device has safe access rights 2.306
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.160
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.653
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login 48.966
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 23.541
And I take note of which tps features are available 8.303
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 4.029
After features/support/hooks.rb:339 0.177
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.198
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.543
Then Tails is running from USB drive "old" 0.235
And all tps features are active 7.902
When I write some files expected to persist 1.259
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.274
And all persistent directories from the old Tails version have safe access rights 1.878
And I take note of which tps features are available 6.187
And I shutdown Tails and wait for the computer to power off 3.993
# 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.605
After features/support/hooks.rb:339 0.145
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.085
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.983
And I log in to a new session 11.504
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.686
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.888
Then the running Tails is installed on USB drive "to_upgrade" 18.528
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 3.593
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.504
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.111
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.200
Then all tps features from the old Tails version are active 1.090
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.189
And the expected persistent files created with the old Tails version are present in the filesystem 1.052
And all persistent directories from the old Tails version have safe access rights 1.615
After features/support/hooks.rb:339 0.716
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:33.269
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.312
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.035
And Tor is ready 13.178
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.314
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.383
Given I shutdown Tails and wait for the computer to power off 5.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.427
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.739
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.108
# 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.201
When the network is plugged 0.037
And Tor is ready 10.603
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.364
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.783
Given I shutdown Tails and wait for the computer to power off 4.012
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.473
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.267
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.038
And Tor is ready 10.374
Then the Upgrader considers the system as up-to-date 0.085
# 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.628
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:339 1.048
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
18.034
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.786
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.579
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.326
After features/support/hooks.rb:339 0.661
After features/support/hooks.rb:108 0.000