Project Number Date
test_Tails_ISO_21565-flatpak-safe 28 07 Sep 2026, 03:18

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:49.151 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:4.354
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.034
When I start Tails from USB drive "old" with network unplugged 47.561
Then the boot device has safe access rights 2.037
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.699
After features/support/hooks.rb:108 0.092
Tags: @product
1:18.838
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 "old" with network unplugged and I login 45.729
Then Tails is running from USB drive "old" 0.183
And I create a persistent partition 22.177
And I take note of which tps features are available 6.053
Then a Tails persistence partition exists on USB drive "old" 0.577
And I shutdown Tails and wait for the computer to power off 4.040
After features/support/hooks.rb:339 0.477
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.284
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.255
Then Tails is running from USB drive "old" 0.200
And all tps features are active 6.451
When I write some files expected to persist 0.820
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.102
And all persistence configuration files have safe access rights 0.222
And all persistent directories from the old Tails version have safe access rights 1.401
And I take note of which tps features are available 5.949
And I shutdown Tails and wait for the computer to power off 3.921
# 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.886
After features/support/hooks.rb:339 0.517
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.997
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.105
And I log in to a new session 11.488
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.568
And I plug USB drive "to_upgrade" 2.184
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.814
Then the running Tails is installed on USB drive "to_upgrade" 17.589
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 1.735
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.409
Then all tps features from the old Tails version are active 0.950
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 1.633
And the expected persistent files created with the old Tails version are present in the filesystem 0.756
And all persistent directories from the old Tails version have safe access rights 1.448
After features/support/hooks.rb:339 0.731
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
3:21.664
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.043
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.311
When the network is plugged 0.033
And Tor is ready 12.801
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.469
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.052
Given I shutdown Tails and wait for the computer to power off 5.190
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.616
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.324
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.085
# 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.155
When the network is plugged 0.036
And Tor is ready 10.391
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.859
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.289
Given I shutdown Tails and wait for the computer to power off 2.548
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.544
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.485
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.071
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.025
And Tor is ready 11.311
Then the Upgrader considers the system as up-to-date 0.109
# 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.285
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.306
After features/support/hooks.rb:339 0.626
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.530
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.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
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.039
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 8.693
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.412
After features/support/hooks.rb:339 0.582
After features/support/hooks.rb:108 0.000