Project Number Date
test_Tails_ISO_21565-flatpak-safe 21 31 Aug 2026, 16:31

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:24.846 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:12.771
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.698
When I start Tails from USB drive "old" with network unplugged 55.239
Then the boot device has safe access rights 2.067
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 1.485
After features/support/hooks.rb:108 0.006
Tags: @product
1:23.801
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login 49.312
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 22.797
And I take note of which tps features are available 6.838
Then a Tails persistence partition exists on USB drive "old" 0.479
And I shutdown Tails and wait for the computer to power off 4.014
After features/support/hooks.rb:339 0.581
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.477
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.148
Then Tails is running from USB drive "old" 0.230
And all tps features are active 7.026
When I write some files expected to persist 1.181
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.238
And all persistent directories from the old Tails version have safe access rights 1.751
And I take note of which tps features are available 6.309
And I shutdown Tails and wait for the computer to power off 2.566
# 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.806
After features/support/hooks.rb:339 0.324
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.764
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.834
And I log in to a new session 14.088
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.710
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.350
Then the running Tails is installed on USB drive "to_upgrade" 18.253
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 2.295
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.268
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.762
Then all tps features from the old Tails version are active 1.148
And Tails is running from USB drive "to_upgrade" 0.215
And the boot device has safe access rights 2.350
And the expected persistent files created with the old Tails version are present in the filesystem 1.005
And all persistent directories from the old Tails version have safe access rights 1.699
After features/support/hooks.rb:339 0.908
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:30.232
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.030
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
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.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.346
When the network is plugged 0.026
And Tor is ready 12.612
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.095
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.522
Given I shutdown Tails and wait for the computer to power off 5.394
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.858
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 9.343
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.193
# 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.241
When the network is plugged 0.031
And Tor is ready 10.405
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.847
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.365
Given I shutdown Tails and wait for the computer to power off 2.588
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.691
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.841
And the file system changes introduced in version 6.3~testoverlayfs are present 0.299
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.206
When the network is plugged 0.058
And Tor is ready 10.050
Then the Upgrader considers the system as up-to-date 0.099
# 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.590
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.393
After features/support/hooks.rb:339 0.684
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
20.529
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.031
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.167
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.022
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.174
After features/support/hooks.rb:339 0.923
After features/support/hooks.rb:108 0.000