Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 40 23 May 2026, 14:20

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:59.188 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:13.225
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.048
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" 12.792
When I start Tails from USB drive "old" with network unplugged 56.052
Then the boot device has safe access rights 2.612
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:335 4.113
After features/support/hooks.rb:104 0.007
Tags: @product
1:25.618
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 53.402
Then Tails is running from USB drive "old" 0.282
And I create a persistent partition 24.180
And I take note of which tps features are available 0.319
Then a Tails persistence partition exists on USB drive "old" 0.533
And I shutdown Tails and wait for the computer to power off 6.834
After features/support/hooks.rb:335 0.229
After features/support/hooks.rb:104 0.006
Tags: @product
1:20.562
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.377
Then Tails is running from USB drive "old" 0.265
And all tps features are active 1.126
When I write some files expected to persist 1.202
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 1.802
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 4.100
# 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.980
After features/support/hooks.rb:335 0.266
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.008
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 7.785
And I log in to a new session 11.996
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.763
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.162
Then the running Tails is installed on USB drive "to_upgrade" 14.783
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:335 2.226
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.765
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.878
Then all tps features from the old Tails version are active 1.070
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 2.559
And the expected persistent files created with the old Tails version are present in the filesystem 1.053
And all persistent directories from the old Tails version have safe access rights 1.840
After features/support/hooks.rb:335 0.983
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:55.061
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 7.881
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.301
When the network is plugged 0.017
And Tor is ready 13.979
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.998
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.186
Given I shutdown Tails and wait for the computer to power off 9.509
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.394
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.100
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.187
When the network is plugged 0.013
And Tor is ready 10.638
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.703
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.410
Given I shutdown Tails and wait for the computer to power off 7.874
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.884
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.182
And the file system changes introduced in version 6.3~testoverlayfs are present 0.421
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.017
And Tor is ready 41.221
Then the Upgrader considers the system as up-to-date 0.106
# 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.305
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.395
After features/support/hooks.rb:335 0.983
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
47.946
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.213
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
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.050
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 40.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.347
After features/support/hooks.rb:335 0.775
After features/support/hooks.rb:104 0.000