Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 71 23 Jun 2026, 14:31

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:42.722 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:8.786
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.221
When I start Tails from USB drive "old" with network unplugged 50.957
Then the boot device has safe access rights 2.840
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 3.768
After features/support/hooks.rb:108 0.063
Tags: @product
1:27.137
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 51.851
Then Tails is running from USB drive "old" 0.200
And I create a persistent partition 23.981
And I take note of which tps features are available 3.879
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 6.618
After features/support/hooks.rb:339 0.180
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.605
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.374
Then Tails is running from USB drive "old" 0.185
And all tps features are active 4.906
When I write some files expected to persist 1.197
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.286
And all persistent directories from the old Tails version have safe access rights 1.843
And I take note of which tps features are available 3.789
And I shutdown Tails and wait for the computer to power off 7.895
# 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.850
After features/support/hooks.rb:339 0.216
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.995
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 7.541
And I log in to a new session 12.524
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.758
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.979
Then the running Tails is installed on USB drive "to_upgrade" 14.713
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 2.279
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.800
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.022
Then all tps features from the old Tails version are active 0.884
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 2.545
And the expected persistent files created with the old Tails version are present in the filesystem 1.259
And all persistent directories from the old Tails version have safe access rights 1.766
After features/support/hooks.rb:339 0.951
After features/support/hooks.rb:108 0.006
3:50.981
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.752
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.203
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.015
And Tor is ready 13.504
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.429
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.380
Given I shutdown Tails and wait for the computer to power off 9.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.087
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.859
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.189
When the network is plugged 0.015
And Tor is ready 10.007
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.971
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.882
Given I shutdown Tails and wait for the computer to power off 7.899
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.559
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.914
And the file system changes introduced in version 6.3~testoverlayfs are present 0.340
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.017
And Tor is ready 11.838
Then the Upgrader considers the system as up-to-date 10.520
# 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.288
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:339 0.902
After features/support/hooks.rb:108 0.046
20.415
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.188
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.805
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.137
After features/support/hooks.rb:339 0.838
After features/support/hooks.rb:108 0.000