Project Number Date
test_Tails_ISO_21548-flatpak-install 9 21 May 2026, 15:15

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:59.748 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:15.830
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.303
When I start Tails from USB drive "old" with network unplugged 56.890
Then the boot device has safe access rights 2.849
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:335 3.725
After features/support/hooks.rb:104 0.010
Tags: @product
1:31.152
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login 55.554
Then Tails is running from USB drive "old" 0.336
And I create a persistent partition 26.030
And I take note of which tps features are available 0.363
Then a Tails persistence partition exists on USB drive "old" 0.586
And I shutdown Tails and wait for the computer to power off 8.215
After features/support/hooks.rb:335 0.273
After features/support/hooks.rb:104 0.009
Tags: @product
1:29.201
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.234
Then Tails is running from USB drive "old" 0.246
And all tps features are active 1.173
When I write some files expected to persist 1.276
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.814
And I take note of which tps features are available 0.168
And I shutdown Tails and wait for the computer to power off 8.312
# 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.457
After features/support/hooks.rb:335 0.084
After features/support/hooks.rb:104 0.007
Tags: @product
2:27.483
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 without a persistent partition and stopped at Tails Greeter's login screen 21.452
And I log in to a new session 14.136
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.793
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.008
Then the running Tails is installed on USB drive "to_upgrade" 16.582
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:335 3.871
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.299
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.128
Then all tps features from the old Tails version are active 0.968
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.704
And the expected persistent files created with the old Tails version are present in the filesystem 1.217
And all persistent directories from the old Tails version have safe access rights 1.981
After features/support/hooks.rb:335 0.997
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:43.063
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 8.676
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
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.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.017
And Tor is ready 13.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.919
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.168
Given I shutdown Tails and wait for the computer to power off 9.441
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.529
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.191
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.269
When the network is plugged 0.014
And Tor is ready 9.680
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.508
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.959
Given I shutdown Tails and wait for the computer to power off 4.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.516
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.239
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.014
And Tor is ready 10.527
Then the Upgrader considers the system as up-to-date 10.545
# 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.672
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.589
After features/support/hooks.rb:335 0.797
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.716
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.862
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.743
After features/support/hooks.rb:335 0.568
After features/support/hooks.rb:104 0.000