Project Number Date
test_Tails_ISO_21565-flatpak-safe 54 28 Sep 2026, 03:25

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 13:12.383 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:2.150
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.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.964
When I start Tails from USB drive "old" with network unplugged 45.374
Then the boot device has safe access rights 2.108
And Tails is running from USB drive "old" 0.178
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 1.562
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.243
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 46.913
Then Tails is running from USB drive "old" 0.187
And I create a persistent partition 22.589
And I take note of which tps features are available 6.075
Then a Tails persistence partition exists on USB drive "old" 0.475
And I shutdown Tails and wait for the computer to power off 3.925
After features/support/hooks.rb:339 0.617
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.933
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.720
Then Tails is running from USB drive "old" 0.171
And all tps features are active 6.706
When I write some files expected to persist 1.023
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.327
And all persistent directories from the old Tails version have safe access rights 1.457
And I take note of which tps features are available 5.882
And I shutdown Tails and wait for the computer to power off 2.532
# 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" 10.856
After features/support/hooks.rb:339 0.334
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.466
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.183
And I log in to a new session 11.821
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.603
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.035
Then the running Tails is installed on USB drive "to_upgrade" 17.388
And I unplug USB drive "to_upgrade" 0.105
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.703
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.727
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.196
Then all tps features from the old Tails version are active 0.978
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 1.957
And the expected persistent files created with the old Tails version are present in the filesystem 0.986
And all persistent directories from the old Tails version have safe access rights 1.328
After features/support/hooks.rb:339 0.892
After features/support/hooks.rb:108 0.007
5:34.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.122
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.309
When the network is plugged 0.026
And Tor is ready 13.232
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:3.726
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.725
Given I shutdown Tails and wait for the computer to power off 5.203
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.147
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.290
And the file system changes introduced in version 6.2~testoverlayfs are present 0.171
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.095
# 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.160
When the network is plugged 0.033
And Tor is ready 9.853
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 13.768
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.533
Given I shutdown Tails and wait for the computer to power off 2.550
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.486
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.965
And the file system changes introduced in version 6.3~testoverlayfs are present 0.312
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.079
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.126
When the network is plugged 0.031
And Tor is ready 10.354
Then the Upgrader considers the system as up-to-date 0.074
# 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 2.974
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.280
After features/support/hooks.rb:339 0.634
After features/support/hooks.rb:108 0.012
31.539
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 7.794
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.491
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.831
After features/support/hooks.rb:339 0.868
After features/support/hooks.rb:108 0.000