Project Number Date
test_Tails_ISO_stable-flatpak 34 02 Oct 2026, 19:46

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:23.721 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:12.809
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.327
When I start Tails from USB drive "old" with network unplugged 55.726
Then the boot device has safe access rights 2.073
And Tails is running from USB drive "old" 0.204
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.033
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.104
After features/support/hooks.rb:339 3.728
After features/support/hooks.rb:108 0.011
Tags: @product
1:22.604
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 47.318
Then Tails is running from USB drive "old" 0.222
And I create a persistent partition 23.893
And I take note of which tps features are available 6.387
Then a Tails persistence partition exists on USB drive "old" 0.563
And I shutdown Tails and wait for the computer to power off 4.130
After features/support/hooks.rb:339 0.269
After features/support/hooks.rb:108 0.012
Tags: @product
1:35.767
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.133
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.138
Then Tails is running from USB drive "old" 0.175
And all tps features are active 7.614
When I write some files expected to persist 1.122
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.276
And all persistent directories from the old Tails version have safe access rights 1.735
And I take note of which tps features are available 6.218
And I shutdown Tails and wait for the computer to power off 4.114
# 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.106
After features/support/hooks.rb:339 0.520
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.819
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.233
And I log in to a new session 11.254
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.605
And I plug USB drive "to_upgrade" 2.272
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.032
Then the running Tails is installed on USB drive "to_upgrade" 17.127
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 1.525
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.118
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.086
Then all tps features from the old Tails version are active 1.012
And Tails is running from USB drive "to_upgrade" 0.174
And the boot device has safe access rights 1.819
And the expected persistent files created with the old Tails version are present in the filesystem 1.067
And all persistent directories from the old Tails version have safe access rights 1.853
After features/support/hooks.rb:339 0.608
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:33.998
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.022
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.024
And Tor is ready 12.319
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.162
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.172
Given I shutdown Tails and wait for the computer to power off 5.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.527
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.962
And the file system changes introduced in version 6.2~testoverlayfs are present 0.182
And only the 6.2~testoverlayfs SquashFS delta is installed 0.032
# 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.181
When the network is plugged 0.026
And Tor is ready 10.117
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.950
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.474
Given I shutdown Tails and wait for the computer to power off 2.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.480
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.803
And the file system changes introduced in version 6.3~testoverlayfs are present 0.287
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.140
When the network is plugged 0.032
And Tor is ready 9.840
Then the Upgrader considers the system as up-to-date 0.123
# 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.648
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.316
After features/support/hooks.rb:339 0.844
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.602
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.866
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 11.034
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.365
After features/support/hooks.rb:339 0.581
After features/support/hooks.rb:108 0.000