Project Number Date
test_Tails_ISO_21548-flatpak-install 4 14 May 2026, 14:25

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:34.441 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:14.877
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.847
When I start Tails from USB drive "old" with network unplugged 56.289
Then the boot device has safe access rights 2.962
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:335 1.427
After features/support/hooks.rb:104 0.025
Tags: @product
1:26.545
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.017
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 56.814
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 24.327
And I take note of which tps features are available 0.345
Then a Tails persistence partition exists on USB drive "old" 0.501
And I shutdown Tails and wait for the computer to power off 4.211
After features/support/hooks.rb:335 0.336
After features/support/hooks.rb:104 0.007
Tags: @product
1:26.687
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.939
Then Tails is running from USB drive "old" 0.447
And all tps features are active 1.430
When I write some files expected to persist 1.553
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 2.079
And I take note of which tps features are available 0.161
And I shutdown Tails and wait for the computer to power off 4.042
# 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" 12.405
After features/support/hooks.rb:335 0.132
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.133
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.600
And I log in to a new session 13.578
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.948
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.622
Then the running Tails is installed on USB drive "to_upgrade" 15.849
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:335 3.738
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.529
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.128
Then all tps features from the old Tails version are active 1.075
And Tails is running from USB drive "to_upgrade" 0.265
And the boot device has safe access rights 2.599
And the expected persistent files created with the old Tails version are present in the filesystem 1.257
And all persistent directories from the old Tails version have safe access rights 2.145
After features/support/hooks.rb:335 0.768
After features/support/hooks.rb:104 0.007
3:44.015
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.268
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.017
And Tor is ready 13.673
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.763
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.758
Given I shutdown Tails and wait for the computer to power off 9.933
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.725
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 1.256
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.218
When the network is plugged 0.034
And Tor is ready 10.514
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.215
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.088
Given I shutdown Tails and wait for the computer to power off 8.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.929
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.308
And the file system changes introduced in version 6.3~testoverlayfs are present 0.424
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.014
And Tor is ready 9.810
Then the Upgrader considers the system as up-to-date 10.508
# 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 4.152
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:335 0.909
After features/support/hooks.rb:104 0.020
19.651
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.319
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 10.197
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.772
After features/support/hooks.rb:335 0.567
After features/support/hooks.rb:104 0.000