Project Number Date
test_Tails_ISO_21565-flatpak-safe 63 02 Oct 2026, 03:21

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:48.175 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.072
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.274
When I start Tails from USB drive "old" with network unplugged 47.216
Then the boot device has safe access rights 1.865
And Tails is running from USB drive "old" 0.215
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.469
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.929
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 47.190
Then Tails is running from USB drive "old" 0.193
And I create a persistent partition 22.963
And I take note of which tps features are available 5.910
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 4.069
After features/support/hooks.rb:339 0.373
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.829
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.193
Then Tails is running from USB drive "old" 0.162
And all tps features are active 6.820
When I write some files expected to persist 1.009
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.142
And all persistence configuration files have safe access rights 0.215
And all persistent directories from the old Tails version have safe access rights 1.470
And I take note of which tps features are available 5.938
And I shutdown Tails and wait for the computer to power off 2.583
# 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.205
After features/support/hooks.rb:339 0.441
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.177
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.267
And I log in to a new session 10.216
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.613
And I plug USB drive "to_upgrade" 2.193
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.672
Then the running Tails is installed on USB drive "to_upgrade" 17.975
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.707
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.848
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.320
Then all tps features from the old Tails version are active 0.954
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.123
And the expected persistent files created with the old Tails version are present in the filesystem 0.757
And all persistent directories from the old Tails version have safe access rights 1.392
After features/support/hooks.rb:339 0.801
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:19.694
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.095
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.170
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.035
And Tor is ready 12.662
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.297
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.833
Given I shutdown Tails and wait for the computer to power off 5.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.151
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.322
And the file system changes introduced in version 6.2~testoverlayfs are present 0.182
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.086
# 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.194
When the network is plugged 0.036
And Tor is ready 10.099
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.314
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.609
Given I shutdown Tails and wait for the computer to power off 2.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.567
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.193
And the file system changes introduced in version 6.3~testoverlayfs are present 0.294
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.043
And Tor is ready 9.983
Then the Upgrader considers the system as up-to-date 0.080
# 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.103
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 0.587
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.624
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.905
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.019
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.404
After features/support/hooks.rb:339 0.506
After features/support/hooks.rb:108 0.000