Project Number Date
test_Tails_ISO_21565-flatpak-safe 97 23 Oct 2026, 03:26

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:20.969 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:6.183
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.021
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.438
When I start Tails from USB drive "old" with network unplugged 48.870
Then the boot device has safe access rights 2.212
And Tails is running from USB drive "old" 0.163
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.165
And I unplug USB drive "old" 0.104
After features/support/hooks.rb:339 1.383
After features/support/hooks.rb:108 0.006
Tags: @product
1:22.454
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 48.550
Then Tails is running from USB drive "old" 0.194
And I create a persistent partition 23.024
And I take note of which tps features are available 5.876
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 4.215
After features/support/hooks.rb:339 0.435
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.026
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.149
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.094
Then Tails is running from USB drive "old" 0.189
And all tps features are active 7.286
When I write some files expected to persist 1.003
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.122
And all persistence configuration files have safe access rights 0.265
And all persistent directories from the old Tails version have safe access rights 1.624
And I take note of which tps features are available 6.400
And I shutdown Tails and wait for the computer to power off 2.732
# 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.157
After features/support/hooks.rb:339 0.254
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.656
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.666
And I log in to a new session 12.210
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.690
And I plug USB drive "to_upgrade" 2.258
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.573
Then the running Tails is installed on USB drive "to_upgrade" 17.985
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 1.815
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.394
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.288
Then all tps features from the old Tails version are active 1.075
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.201
And the expected persistent files created with the old Tails version are present in the filesystem 1.077
And all persistent directories from the old Tails version have safe access rights 1.420
After features/support/hooks.rb:339 0.780
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:41.516
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 21.455
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.050
And Tor is ready 13.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.889
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.220
Given I shutdown Tails and wait for the computer to power off 5.457
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.889
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.521
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.178
When the network is plugged 0.036
And Tor is ready 10.629
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.608
Given I shutdown Tails and wait for the computer to power off 2.571
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.604
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.334
And the file system changes introduced in version 6.3~testoverlayfs are present 0.305
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.032
And Tor is ready 10.766
Then the Upgrader considers the system as up-to-date 0.094
# 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.209
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.533
After features/support/hooks.rb:339 0.912
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
17.738
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.785
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
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.068
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.319
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.289
After features/support/hooks.rb:339 1.040
After features/support/hooks.rb:108 0.000