Project Number Date
test_Tails_ISO_21565-flatpak-safe 101 26 Oct 2026, 18:55

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:27.371 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:13.185
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.331
When I start Tails from USB drive "old" with network unplugged 55.515
Then the boot device has safe access rights 2.633
And Tails is running from USB drive "old" 0.193
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.361
After features/support/hooks.rb:108 0.012
Tags: @product
1:23.026
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login 47.732
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 23.940
And I take note of which tps features are available 6.472
Then a Tails persistence partition exists on USB drive "old" 0.473
And I shutdown Tails and wait for the computer to power off 4.098
After features/support/hooks.rb:339 0.389
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.263
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.296
Then Tails is running from USB drive "old" 0.223
And all tps features are active 6.838
When I write some files expected to persist 1.219
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.284
And all persistent directories from the old Tails version have safe access rights 1.506
And I take note of which tps features are available 6.759
And I shutdown Tails and wait for the computer to power off 2.567
# 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.294
After features/support/hooks.rb:339 0.604
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.698
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.544
And I log in to a new session 13.031
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.722
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.210
Then the running Tails is installed on USB drive "to_upgrade" 19.657
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 1.864
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.651
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.682
Then all tps features from the old Tails version are active 1.070
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.005
And the expected persistent files created with the old Tails version are present in the filesystem 0.885
And all persistent directories from the old Tails version have safe access rights 1.673
After features/support/hooks.rb:339 0.570
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:37.534
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.147
And no SquashFS delta is installed 0.088
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.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.038
And Tor is ready 11.808
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.134
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.813
Given I shutdown Tails and wait for the computer to power off 6.791
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.783
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.846
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.086
# 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.175
When the network is plugged 0.024
And Tor is ready 10.673
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.666
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.482
Given I shutdown Tails and wait for the computer to power off 4.033
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.579
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.246
And the file system changes introduced in version 6.3~testoverlayfs are present 0.297
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.093
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.035
And Tor is ready 10.778
Then the Upgrader considers the system as up-to-date 0.087
# 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.208
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.321
After features/support/hooks.rb:339 0.816
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
18.011
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.051
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.052
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.026
And Tor is ready 8.683
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.961
After features/support/hooks.rb:339 0.679
After features/support/hooks.rb:108 0.000