Project Number Date
test_Tails_ISO_21565-flatpak-safe 104 27 Oct 2026, 18:54

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:35.734 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.295
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.679
When I start Tails from USB drive "old" with network unplugged 45.951
Then the boot device has safe access rights 1.977
And Tails is running from USB drive "old" 0.183
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.105
After features/support/hooks.rb:339 3.968
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.361
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 50.624
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 23.683
And I take note of which tps features are available 6.566
Then a Tails persistence partition exists on USB drive "old" 0.878
And I shutdown Tails and wait for the computer to power off 4.251
After features/support/hooks.rb:339 0.470
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.149
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.112
Then Tails is running from USB drive "old" 0.202
And all tps features are active 7.553
When I write some files expected to persist 1.134
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.942
And I take note of which tps features are available 6.906
And I shutdown Tails and wait for the computer to power off 3.977
# 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.786
After features/support/hooks.rb:339 0.135
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.967
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.795
And I log in to a new session 12.392
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.100
And I plug USB drive "to_upgrade" 2.613
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.399
Then the running Tails is installed on USB drive "to_upgrade" 19.163
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.356
After features/support/hooks.rb:339 2.219
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.134
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.295
Then all tps features from the old Tails version are active 1.159
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 2.573
And the expected persistent files created with the old Tails version are present in the filesystem 1.001
And all persistent directories from the old Tails version have safe access rights 1.682
After features/support/hooks.rb:339 0.562
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
3:39.241
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.887
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.182
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.026
And Tor is ready 13.353
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.121
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.872
Given I shutdown Tails and wait for the computer to power off 5.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.638
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.583
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
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.104
# 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.229
When the network is plugged 0.030
And Tor is ready 10.509
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.004
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.074
Given I shutdown Tails and wait for the computer to power off 4.153
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.184
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.754
And the file system changes introduced in version 6.3~testoverlayfs are present 0.303
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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.166
When the network is plugged 0.027
And Tor is ready 10.390
Then the Upgrader considers the system as up-to-date 0.102
# 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.488
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.421
After features/support/hooks.rb:339 0.665
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
19.584
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 with a persistent partition enabled and logged in 7.968
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 10.970
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.313
After features/support/hooks.rb:339 0.645
After features/support/hooks.rb:108 0.000