Project Number Date
test_Tails_ISO_21565-flatpak-safe 118 03 Nov 2026, 03:36

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 10:44.197 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:5.945
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.308
When I start Tails from USB drive "old" with network unplugged 49.082
Then the boot device has safe access rights 1.903
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.153
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.696
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.823
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 45.682
Then Tails is running from USB drive "old" 0.172
And I create a persistent partition 22.515
And I take note of which tps features are available 5.847
Then a Tails persistence partition exists on USB drive "old" 0.563
And I shutdown Tails and wait for the computer to power off 3.970
After features/support/hooks.rb:339 0.479
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.147
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.455
Then Tails is running from USB drive "old" 0.192
And all tps features are active 6.607
When I write some files expected to persist 1.051
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
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.598
And I take note of which tps features are available 6.027
And I shutdown Tails and wait for the computer to power off 2.531
# 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.154
After features/support/hooks.rb:339 0.183
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.845
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.131
And I log in to a new session 10.327
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.604
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.377
Then the running Tails is installed on USB drive "to_upgrade" 17.905
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 1.596
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.846
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.374
Then all tps features from the old Tails version are active 0.933
And Tails is running from USB drive "to_upgrade" 0.187
And the boot device has safe access rights 1.914
And the expected persistent files created with the old Tails version are present in the filesystem 0.841
And all persistent directories from the old Tails version have safe access rights 1.516
After features/support/hooks.rb:339 0.770
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:18.323
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 with a persistent partition enabled and logged in 8.242
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.175
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.304
When the network is plugged 0.026
And Tor is ready 11.198
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.979
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.238
Given I shutdown Tails and wait for the computer to power off 5.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.238
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.882
And the file system changes introduced in version 6.2~testoverlayfs are present 0.159
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.089
# 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.165
When the network is plugged 0.033
And Tor is ready 10.122
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.282
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.381
Given I shutdown Tails and wait for the computer to power off 2.665
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.021
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.366
And the file system changes introduced in version 6.3~testoverlayfs are present 0.343
And only the 6.3~testoverlayfs SquashFS delta is installed 0.032
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.140
When the network is plugged 0.027
And Tor is ready 9.918
Then the Upgrader considers the system as up-to-date 0.084
# 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.193
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.271
After features/support/hooks.rb:339 0.975
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.266
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 with a persistent partition enabled and logged in 8.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
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.045
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.400
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.428
After features/support/hooks.rb:339 0.866
After features/support/hooks.rb:108 0.000