Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 29 16 May 2026, 14:11

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:5.352 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:7.157
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 12.796
When I start Tails from USB drive "old" with network unplugged 49.761
Then the boot device has safe access rights 2.820
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:335 1.429
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.010
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 51.503
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 24.033
And I take note of which tps features are available 0.461
Then a Tails persistence partition exists on USB drive "old" 0.533
And I shutdown Tails and wait for the computer to power off 8.175
After features/support/hooks.rb:335 0.313
After features/support/hooks.rb:104 0.007
Tags: @product
1:22.684
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.906
Then Tails is running from USB drive "old" 0.236
And all tps features are active 1.150
When I write some files expected to persist 1.383
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 1.767
And I take note of which tps features are available 0.169
And I shutdown Tails and wait for the computer to power off 7.777
# 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.777
After features/support/hooks.rb:335 0.140
After features/support/hooks.rb:104 0.006
Tags: @product
2:7.530
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 without a persistent partition and stopped at Tails Greeter's login screen 7.343
And I log in to a new session 11.461
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.689
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.951
Then the running Tails is installed on USB drive "to_upgrade" 14.610
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:335 2.414
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.263
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.353
Then all tps features from the old Tails version are active 1.049
And Tails is running from USB drive "to_upgrade" 0.268
And the boot device has safe access rights 2.493
And the expected persistent files created with the old Tails version are present in the filesystem 1.103
And all persistent directories from the old Tails version have safe access rights 1.943
After features/support/hooks.rb:335 0.965
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:36.313
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.895
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.347
When the network is plugged 0.015
And Tor is ready 13.424
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.937
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.428
Given I shutdown Tails and wait for the computer to power off 9.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.495
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 0.995
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.186
When the network is plugged 0.019
And Tor is ready 10.933
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.790
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.176
Given I shutdown Tails and wait for the computer to power off 7.850
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.317
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.093
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.016
And Tor is ready 11.163
Then the Upgrader considers the system as up-to-date 10.541
# 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.225
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:335 1.039
After features/support/hooks.rb:104 0.017
Tags: @product @automatic_upgrade
20.393
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.320
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.271
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.497
After features/support/hooks.rb:335 0.793
After features/support/hooks.rb:104 0.000