Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 41 24 May 2026, 14:13

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:3.731 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:11.989
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 12.831
When I start Tails from USB drive "old" with network unplugged 54.759
Then the boot device has safe access rights 2.630
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:335 3.576
After features/support/hooks.rb:104 0.007
Tags: @product
1:26.750
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 52.616
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 24.833
And I take note of which tps features are available 0.420
Then a Tails persistence partition exists on USB drive "old" 0.615
And I shutdown Tails and wait for the computer to power off 7.945
After features/support/hooks.rb:335 0.648
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.146
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.510
Then Tails is running from USB drive "old" 0.210
And all tps features are active 1.123
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.243
And all persistent directories from the old Tails version have safe access rights 1.754
And I take note of which tps features are available 0.162
And I shutdown Tails and wait for the computer to power off 8.197
# 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.502
After features/support/hooks.rb:335 0.146
After features/support/hooks.rb:104 0.007
Tags: @product
2:8.923
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 without a persistent partition and stopped at Tails Greeter's login screen 8.032
And I log in to a new session 12.291
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.690
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.519
Then the running Tails is installed on USB drive "to_upgrade" 13.862
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:335 2.402
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.836
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.113
Then all tps features from the old Tails version are active 0.927
And Tails is running from USB drive "to_upgrade" 0.303
And the boot device has safe access rights 2.602
And the expected persistent files created with the old Tails version are present in the filesystem 1.011
And all persistent directories from the old Tails version have safe access rights 1.823
After features/support/hooks.rb:335 0.849
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:25.876
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 7.587
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.019
And Tor is ready 12.786
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.702
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.422
Given I shutdown Tails and wait for the computer to power off 5.413
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.297
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.097
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.035
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.179
When the network is plugged 0.018
And Tor is ready 10.524
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.505
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.004
Given I shutdown Tails and wait for the computer to power off 3.987
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.359
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.030
And the file system changes introduced in version 6.3~testoverlayfs are present 0.338
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.015
And Tor is ready 10.662
Then the Upgrader considers the system as up-to-date 10.508
# 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.124
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.454
After features/support/hooks.rb:335 0.906
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
20.208
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 7.147
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.043
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.732
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.027
After features/support/hooks.rb:335 1.020
After features/support/hooks.rb:104 0.000