Project Number Date
test_Tails_ISO_21565-flatpak-safe 29 08 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 11:6.506 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:11.671
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
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" 13.372
When I start Tails from USB drive "old" with network unplugged 54.852
Then the boot device has safe access rights 1.785
And Tails is running from USB drive "old" 0.162
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.033
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 3.496
After features/support/hooks.rb:108 0.020
Tags: @product
1:19.945
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 46.737
Then Tails is running from USB drive "old" 0.167
And I create a persistent partition 22.640
And I take note of which tps features are available 5.886
Then a Tails persistence partition exists on USB drive "old" 0.430
And I shutdown Tails and wait for the computer to power off 4.012
After features/support/hooks.rb:339 0.426
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.467
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.198
Then Tails is running from USB drive "old" 0.199
And all tps features are active 7.078
When I write some files expected to persist 0.940
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.221
And all persistent directories from the old Tails version have safe access rights 1.404
And I take note of which tps features are available 5.485
And I shutdown Tails and wait for the computer to power off 2.537
# 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.147
After features/support/hooks.rb:339 0.336
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.735
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 without a persistent partition and stopped at Tails Greeter's login screen 8.261
And I log in to a new session 13.021
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.574
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.448
Then the running Tails is installed on USB drive "to_upgrade" 16.958
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 2.020
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.382
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.530
Then all tps features from the old Tails version are active 1.028
And Tails is running from USB drive "to_upgrade" 0.177
And the boot device has safe access rights 2.135
And the expected persistent files created with the old Tails version are present in the filesystem 0.855
And all persistent directories from the old Tails version have safe access rights 1.578
After features/support/hooks.rb:339 0.760
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:31.029
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.877
And no SquashFS delta is installed 0.061
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.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.180
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.308
When the network is plugged 0.027
And Tor is ready 13.121
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.305
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.643
Given I shutdown Tails and wait for the computer to power off 5.388
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.934
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 7.635
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.027
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.096
# 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.152
When the network is plugged 0.033
And Tor is ready 10.140
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.380
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.693
Given I shutdown Tails and wait for the computer to power off 2.537
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.065
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.084
And the file system changes introduced in version 6.3~testoverlayfs are present 0.289
And only the 6.3~testoverlayfs SquashFS delta is installed 0.033
# 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.081
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.165
When the network is plugged 0.039
And Tor is ready 10.240
Then the Upgrader considers the system as up-to-date 10.392
# 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.198
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:339 0.825
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.274
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.709
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
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.038
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 10.929
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.292
After features/support/hooks.rb:339 0.845
After features/support/hooks.rb:108 0.000