Project Number Date
test_Tails_ISO_stable-flatpak 41 09 Oct 2026, 19:45

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 10:51.906 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
56.233
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.091
When I start Tails from USB drive "old" with network unplugged 39.633
Then the boot device has safe access rights 1.777
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.106
After features/support/hooks.rb:339 3.750
After features/support/hooks.rb:108 0.038
Tags: @product
1:21.464
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 48.146
Then Tails is running from USB drive "old" 0.217
And I create a persistent partition 22.757
And I take note of which tps features are available 5.832
Then a Tails persistence partition exists on USB drive "old" 0.476
And I shutdown Tails and wait for the computer to power off 3.961
After features/support/hooks.rb:339 0.379
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.525
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.844
Then Tails is running from USB drive "old" 0.208
And all tps features are active 7.393
When I write some files expected to persist 1.208
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.119
And all persistence configuration files have safe access rights 0.208
And all persistent directories from the old Tails version have safe access rights 1.650
And I take note of which tps features are available 5.933
And I shutdown Tails and wait for the computer to power off 2.682
# 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.188
After features/support/hooks.rb:339 0.275
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.835
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.066
And I log in to a new session 11.616
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.657
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.648
Then the running Tails is installed on USB drive "to_upgrade" 17.145
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:339 1.666
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.224
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.022
Then all tps features from the old Tails version are active 1.069
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 1.938
And the expected persistent files created with the old Tails version are present in the filesystem 1.209
And all persistent directories from the old Tails version have safe access rights 1.669
After features/support/hooks.rb:339 0.966
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:27.860
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 7.961
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.168
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.287
When the network is plugged 0.026
And Tor is ready 14.102
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.040
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.266
Given I shutdown Tails and wait for the computer to power off 5.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.286
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.610
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.112
# 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.159
When the network is plugged 0.032
And Tor is ready 10.027
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.923
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.622
Given I shutdown Tails and wait for the computer to power off 3.922
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.835
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.855
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.051
# 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.089
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.036
And Tor is ready 10.224
Then the Upgrader considers the system as up-to-date 0.122
# 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.526
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.287
After features/support/hooks.rb:339 0.984
After features/support/hooks.rb:108 0.041
Tags: @product @automatic_upgrade
18.759
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 7.765
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.169
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 8.335
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.379
After features/support/hooks.rb:339 1.172
After features/support/hooks.rb:108 0.000