Project Number Date
test_Tails_ISO_21565-flatpak-safe 115 02 Nov 2026, 03:38

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:52.322 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.679
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.134
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.024
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 54.045
Then the boot device has safe access rights 1.946
And Tails is running from USB drive "old" 0.147
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.128
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 3.384
After features/support/hooks.rb:108 0.007
Tags: @product
1:20.922
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 46.990
Then Tails is running from USB drive "old" 0.197
And I create a persistent partition 22.090
And I take note of which tps features are available 6.019
Then a Tails persistence partition exists on USB drive "old" 0.516
And I shutdown Tails and wait for the computer to power off 5.033
After features/support/hooks.rb:339 0.466
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.579
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.872
Then Tails is running from USB drive "old" 0.228
And all tps features are active 6.919
When I write some files expected to persist 1.008
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.113
And all persistence configuration files have safe access rights 0.204
And all persistent directories from the old Tails version have safe access rights 1.659
And I take note of which tps features are available 5.866
And I shutdown Tails and wait for the computer to power off 2.521
# 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.105
After features/support/hooks.rb:339 0.226
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.203
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.102
And I log in to a new session 10.882
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.607
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.182
Then the running Tails is installed on USB drive "to_upgrade" 16.973
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.642
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.244
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.442
Then all tps features from the old Tails version are active 0.982
And Tails is running from USB drive "to_upgrade" 0.201
And the boot device has safe access rights 1.970
And the expected persistent files created with the old Tails version are present in the filesystem 0.878
And all persistent directories from the old Tails version have safe access rights 1.674
After features/support/hooks.rb:339 0.878
After features/support/hooks.rb:108 0.011
3:20.823
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.046
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.026
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.278
When the network is plugged 0.027
And Tor is ready 10.627
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.478
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.268
Given I shutdown Tails and wait for the computer to power off 5.185
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.004
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.661
And the file system changes introduced in version 6.2~testoverlayfs are present 0.173
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.174
When the network is plugged 0.035
And Tor is ready 10.061
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.830
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.063
Given I shutdown Tails and wait for the computer to power off 2.524
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.153
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.375
And the file system changes introduced in version 6.3~testoverlayfs are present 0.229
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.087
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.024
And Tor is ready 9.997
Then the Upgrader considers the system as up-to-date 0.088
# 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.159
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.934
After features/support/hooks.rb:108 0.009
16.870
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.735
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
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.027
And Tor is ready 7.944
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.866
After features/support/hooks.rb:339 0.923
After features/support/hooks.rb:108 0.000