Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 38 21 May 2026, 15:40

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 12:8.571 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:21.447
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.199
When I start Tails from USB drive "old" with network unplugged 1:2.461
Then the boot device has safe access rights 2.838
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:335 1.647
After features/support/hooks.rb:104 0.020
Tags: @product
1:32.768
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.012
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login 57.564
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 26.820
And I take note of which tps features are available 0.426
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 6.978
After features/support/hooks.rb:335 0.627
After features/support/hooks.rb:104 0.007
Tags: @product
1:34.664
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.080
Then Tails is running from USB drive "old" 0.323
And all tps features are active 1.876
When I write some files expected to persist 1.525
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.461
And all persistent directories from the old Tails version have safe access rights 2.140
And I take note of which tps features are available 0.178
And I shutdown Tails and wait for the computer to power off 8.326
# 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" 13.437
After features/support/hooks.rb:335 0.210
After features/support/hooks.rb:104 0.016
Tags: @product
2:16.706
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.529
And I log in to a new session 14.078
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.838
And I plug USB drive "to_upgrade" 2.309
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.029
Then the running Tails is installed on USB drive "to_upgrade" 17.623
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.159
After features/support/hooks.rb:335 2.726
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.320
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.930
Then all tps features from the old Tails version are active 1.089
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 2.721
And the expected persistent files created with the old Tails version are present in the filesystem 1.110
And all persistent directories from the old Tails version have safe access rights 2.083
After features/support/hooks.rb:335 0.956
After features/support/hooks.rb:104 0.019
Tags: @product @automatic_upgrade
3:48.575
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.633
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
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.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.015
And Tor is ready 13.459
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.019
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.075
Given I shutdown Tails and wait for the computer to power off 10.087
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.390
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.243
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.220
When the network is plugged 0.014
And Tor is ready 10.250
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.109
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.800
Given I shutdown Tails and wait for the computer to power off 4.180
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.623
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.376
And the file system changes introduced in version 6.3~testoverlayfs are present 0.403
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.017
And Tor is ready 9.999
Then the Upgrader considers the system as up-to-date 10.691
# 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.707
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.437
After features/support/hooks.rb:335 0.941
After features/support/hooks.rb:104 0.022
Tags: @product @automatic_upgrade
21.088
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.510
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.050
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.735
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.474
After features/support/hooks.rb:335 0.660
After features/support/hooks.rb:104 0.000