Project Number Date
test_Tails_ISO_21548-flatpak-install 8 18 May 2026, 14:24

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:25.164 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:3.318
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.292
When I start Tails from USB drive "old" with network unplugged 44.917
Then the boot device has safe access rights 3.292
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:335 1.486
After features/support/hooks.rb:104 0.008
Tags: @product
1:29.231
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 53.935
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 25.769
And I take note of which tps features are available 0.394
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 8.229
After features/support/hooks.rb:335 0.190
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.236
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.199
Then Tails is running from USB drive "old" 0.294
And all tps features are active 1.054
When I write some files expected to persist 1.547
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.257
And all persistent directories from the old Tails version have safe access rights 2.198
And I take note of which tps features are available 0.188
And I shutdown Tails and wait for the computer to power off 8.123
# 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.106
After features/support/hooks.rb:335 0.125
After features/support/hooks.rb:104 0.006
Tags: @product
2:11.182
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 without a persistent partition and stopped at Tails Greeter's login screen 7.949
And I log in to a new session 12.946
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.002
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.294
Then the running Tails is installed on USB drive "to_upgrade" 15.486
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:335 2.555
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.935
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.795
Then all tps features from the old Tails version are active 1.184
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.144
And the expected persistent files created with the old Tails version are present in the filesystem 1.316
And all persistent directories from the old Tails version have safe access rights 2.114
After features/support/hooks.rb:335 0.819
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:41.815
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 with a persistent partition enabled and logged in 8.117
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
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.431
When the network is plugged 0.018
And Tor is ready 13.479
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.428
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.608
Given I shutdown Tails and wait for the computer to power off 7.230
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.892
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.233
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.204
When the network is plugged 0.022
And Tor is ready 11.545
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.733
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.230
Given I shutdown Tails and wait for the computer to power off 8.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.672
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.214
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.016
And Tor is ready 10.067
Then the Upgrader considers the system as up-to-date 10.669
# 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.278
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.349
After features/support/hooks.rb:335 0.715
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.445
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 with a persistent partition enabled and logged in 7.138
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.397
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.556
After features/support/hooks.rb:335 0.767
After features/support/hooks.rb:104 0.000