Project Number Date
test_Tails_ISO_21565-flatpak-safe 82 09 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 11:14.747 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:13.866
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.613
When I start Tails from USB drive "old" with network unplugged 55.672
Then the boot device has safe access rights 2.725
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 1.214
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.907
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 47.797
Then Tails is running from USB drive "old" 0.201
And I create a persistent partition 23.826
And I take note of which tps features are available 6.457
Then a Tails persistence partition exists on USB drive "old" 0.644
And I shutdown Tails and wait for the computer to power off 3.896
After features/support/hooks.rb:339 0.406
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.232
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.695
Then Tails is running from USB drive "old" 0.293
And all tps features are active 6.643
When I write some files expected to persist 1.150
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.141
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.572
And I take note of which tps features are available 6.504
And I shutdown Tails and wait for the computer to power off 2.554
# 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.265
After features/support/hooks.rb:339 0.570
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.035
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.609
And I log in to a new session 11.264
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.634
And I plug USB drive "to_upgrade" 2.434
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.125
Then the running Tails is installed on USB drive "to_upgrade" 17.728
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 1.592
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.599
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 1:2.212
Then all tps features from the old Tails version are active 1.055
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.191
And the expected persistent files created with the old Tails version are present in the filesystem 1.080
And all persistent directories from the old Tails version have safe access rights 1.757
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
3:26.912
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.319
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.025
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.300
When the network is plugged 0.028
And Tor is ready 12.107
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.150
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.573
Given I shutdown Tails and wait for the computer to power off 5.189
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.502
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.819
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
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.093
# 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.148
When the network is plugged 0.035
And Tor is ready 10.133
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.897
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.913
Given I shutdown Tails and wait for the computer to power off 2.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.001
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.245
And the file system changes introduced in version 6.3~testoverlayfs are present 0.303
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.105
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.034
And Tor is ready 10.471
Then the Upgrader considers the system as up-to-date 0.111
# 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.518
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.318
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
19.194
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.824
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 10.052
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.898
After features/support/hooks.rb:339 0.938
After features/support/hooks.rb:108 0.000