Project Number Date
test_Tails_ISO_21548-flatpak-install 2 12 May 2026, 14:49

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 13:32.379 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:22.169
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.092
When I start Tails from USB drive "old" with network unplugged 1:3.286
Then the boot device has safe access rights 3.007
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:335 1.330
After features/support/hooks.rb:104 0.010
Tags: @product
1:35.742
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 59.406
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 26.642
And I take note of which tps features are available 1.128
Then a Tails persistence partition exists on USB drive "old" 0.908
And I shutdown Tails and wait for the computer to power off 7.299
After features/support/hooks.rb:335 0.193
After features/support/hooks.rb:104 0.008
Tags: @product
1:37.486
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.864
Then Tails is running from USB drive "old" 0.258
And all tps features are active 1.416
When I write some files expected to persist 1.854
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.511
And all persistent directories from the old Tails version have safe access rights 2.163
And I take note of which tps features are available 0.214
And I shutdown Tails and wait for the computer to power off 8.438
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.479
After features/support/hooks.rb:335 0.346
After features/support/hooks.rb:104 0.008
Tags: @product
2:17.735
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.418
And I log in to a new session 14.265
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.840
And I plug USB drive "to_upgrade" 2.267
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.283
Then the running Tails is installed on USB drive "to_upgrade" 19.293
And I unplug USB drive "to_upgrade" 0.196
And I unplug USB drive "__internal" 0.169
After features/support/hooks.rb:335 0.846
After features/support/hooks.rb:104 0.000
Tags: @product
1:18.983
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.606
Then all tps features from the old Tails version are active 1.028
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 3.464
And the expected persistent files created with the old Tails version are present in the filesystem 1.388
And all persistent directories from the old Tails version have safe access rights 2.145
After features/support/hooks.rb:335 0.865
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
4:51.240
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 9.195
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.022
And Tor is ready 23.137
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.536
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.392
Given I shutdown Tails and wait for the computer to power off 15.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.836
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.332
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.203
# 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.257
When the network is plugged 0.021
And Tor is ready 22.047
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.522
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.399
Given I shutdown Tails and wait for the computer to power off 17.162
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.685
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.404
And the file system changes introduced in version 6.3~testoverlayfs are present 0.425
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.251
When the network is plugged 0.020
And Tor is ready 22.090
Then the Upgrader considers the system as up-to-date 0.124
# 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.748
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.429
After features/support/hooks.rb:335 0.793
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
29.023
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.583
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 19.513
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.504
After features/support/hooks.rb:335 0.751
After features/support/hooks.rb:104 0.000