Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 21 12 May 2026, 15:25

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 13:25.768 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:26.748
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 14.078
When I start Tails from USB drive "old" with network unplugged 1:7.426
Then the boot device has safe access rights 3.333
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.254
And I unplug USB drive "old" 0.163
After features/support/hooks.rb:335 1.782
After features/support/hooks.rb:104 0.016
Tags: @product
1:34.434
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 59.467
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 25.091
And I take note of which tps features are available 0.760
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 8.150
After features/support/hooks.rb:335 0.435
After features/support/hooks.rb:104 0.008
Tags: @product
1:32.743
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.023
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.082
Then Tails is running from USB drive "old" 0.306
And all tps features are active 1.261
When I write some files expected to persist 1.242
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.423
And all persistent directories from the old Tails version have safe access rights 1.905
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 8.223
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.889
After features/support/hooks.rb:335 0.628
After features/support/hooks.rb:104 0.009
Tags: @product
2:16.860
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.652
And I log in to a new session 14.541
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.112
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.204
Then the running Tails is installed on USB drive "to_upgrade" 17.660
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:335 2.608
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.567
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.197
Then all tps features from the old Tails version are active 1.252
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 3.226
And the expected persistent files created with the old Tails version are present in the filesystem 1.319
And all persistent directories from the old Tails version have safe access rights 2.205
After features/support/hooks.rb:335 0.748
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
4:52.369
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 with a persistent partition enabled and logged in 8.166
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.513
When the network is plugged 0.014
And Tor is ready 23.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.621
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.306
Given I shutdown Tails and wait for the computer to power off 19.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.280
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.119
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.240
When the network is plugged 0.020
And Tor is ready 20.790
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.779
Given I shutdown Tails and wait for the computer to power off 17.745
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.168
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.217
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.256
When the network is plugged 0.015
And Tor is ready 21.610
Then the Upgrader considers the system as up-to-date 0.112
# 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 5.204
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.544
After features/support/hooks.rb:335 0.734
After features/support/hooks.rb:104 0.041
Tags: @product @automatic_upgrade
28.043
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.958
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 19.348
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.417
After features/support/hooks.rb:335 0.769
After features/support/hooks.rb:104 0.000