Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 44 26 May 2026, 18:29

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:58.683 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:14.383
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 13.947
When I start Tails from USB drive "old" with network unplugged 55.366
Then the boot device has safe access rights 3.090
And Tails is running from USB drive "old" 0.258
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:335 1.678
After features/support/hooks.rb:104 0.008
Tags: @product
1:31.305
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 57.049
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 25.947
And I take note of which tps features are available 0.372
Then a Tails persistence partition exists on USB drive "old" 0.571
And I shutdown Tails and wait for the computer to power off 7.022
After features/support/hooks.rb:335 0.664
After features/support/hooks.rb:104 0.009
Tags: @product
1:33.236
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.508
Then Tails is running from USB drive "old" 0.258
And all tps features are active 1.269
When I write some files expected to persist 1.661
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.324
And all persistent directories from the old Tails version have safe access rights 2.103
And I take note of which tps features are available 0.176
And I shutdown Tails and wait for the computer to power off 8.114
# 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" 12.539
After features/support/hooks.rb:335 0.149
After features/support/hooks.rb:104 0.007
Tags: @product
2:14.851
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.367
And I log in to a new session 14.534
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.929
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.570
Then the running Tails is installed on USB drive "to_upgrade" 15.850
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:335 2.695
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.298
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.480
Then all tps features from the old Tails version are active 1.173
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 3.002
And the expected persistent files created with the old Tails version are present in the filesystem 1.294
And all persistent directories from the old Tails version have safe access rights 2.051
After features/support/hooks.rb:335 0.985
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
3:52.430
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.368
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.403
When the network is plugged 0.014
And Tor is ready 12.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.527
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.788
Given I shutdown Tails and wait for the computer to power off 9.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.289
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.379
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.263
When the network is plugged 0.038
And Tor is ready 12.670
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.987
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.920
Given I shutdown Tails and wait for the computer to power off 8.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.407
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.312
And the file system changes introduced in version 6.3~testoverlayfs are present 0.381
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.019
And Tor is ready 10.098
Then the Upgrader considers the system as up-to-date 10.534
# 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.267
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.385
After features/support/hooks.rb:335 1.058
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
21.177
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.759
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.378
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.718
After features/support/hooks.rb:335 1.069
After features/support/hooks.rb:104 0.000