Project Number Date
test_Tails_ISO_21565-flatpak-safe 71 05 Oct 2026, 20:57

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:30.202 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:19.267
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.074
When I start Tails from USB drive "old" with network unplugged 1:2.092
Then the boot device has safe access rights 2.342
And Tails is running from USB drive "old" 0.215
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.162
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 1.424
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.187
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 47.365
Then Tails is running from USB drive "old" 0.198
And I create a persistent partition 22.760
And I take note of which tps features are available 5.991
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 4.229
After features/support/hooks.rb:339 0.191
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.906
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.202
Then Tails is running from USB drive "old" 0.236
And all tps features are active 6.835
When I write some files expected to persist 1.106
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.293
And all persistent directories from the old Tails version have safe access rights 1.385
And I take note of which tps features are available 6.299
And I shutdown Tails and wait for the computer to power off 2.695
# 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.572
After features/support/hooks.rb:339 0.454
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.377
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.728
And I log in to a new session 11.092
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.644
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.945
Then the running Tails is installed on USB drive "to_upgrade" 17.492
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.809
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.943
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.127
Then all tps features from the old Tails version are active 1.074
And Tails is running from USB drive "to_upgrade" 0.155
And the boot device has safe access rights 1.977
And the expected persistent files created with the old Tails version are present in the filesystem 0.973
And all persistent directories from the old Tails version have safe access rights 1.553
After features/support/hooks.rb:339 0.711
After features/support/hooks.rb:108 0.005
3:40.386
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.171
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.306
When the network is plugged 0.028
And Tor is ready 11.556
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.332
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.760
Given I shutdown Tails and wait for the computer to power off 5.352
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.882
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.119
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.199
When the network is plugged 0.036
And Tor is ready 10.432
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.336
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.340
Given I shutdown Tails and wait for the computer to power off 3.956
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.340
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.968
And the file system changes introduced in version 6.3~testoverlayfs are present 0.318
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.149
When the network is plugged 0.022
And Tor is ready 10.827
Then the Upgrader considers the system as up-to-date 10.449
# 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.110
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.302
After features/support/hooks.rb:339 0.990
After features/support/hooks.rb:108 0.010
19.131
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.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 9.663
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.991
After features/support/hooks.rb:339 0.594
After features/support/hooks.rb:108 0.000