Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 48 01 Jun 2026, 18:53

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:0.717 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:6.639
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.128
When I start Tails from USB drive "old" with network unplugged 49.373
Then the boot device has safe access rights 2.417
And Tails is running from USB drive "old" 0.217
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:335 3.692
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.450
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 53.413
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 24.642
And I take note of which tps features are available 0.314
Then a Tails persistence partition exists on USB drive "old" 0.584
And I shutdown Tails and wait for the computer to power off 8.217
After features/support/hooks.rb:335 0.412
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.386
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.937
Then Tails is running from USB drive "old" 0.324
And all tps features are active 1.030
When I write some files expected to persist 1.213
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.725
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 7.798
# 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.663
After features/support/hooks.rb:335 0.461
After features/support/hooks.rb:104 0.007
Tags: @product
2:8.562
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.008
And I log in to a new session 12.112
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.652
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.089
Then the running Tails is installed on USB drive "to_upgrade" 14.148
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:335 2.294
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.287
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.583
Then all tps features from the old Tails version are active 0.937
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.374
And the expected persistent files created with the old Tails version are present in the filesystem 1.232
And all persistent directories from the old Tails version have safe access rights 1.849
After features/support/hooks.rb:335 0.953
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:28.466
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.620
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.022
And Tor is ready 12.194
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.564
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.274
Given I shutdown Tails and wait for the computer to power off 6.916
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.540
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.215
When the network is plugged 0.013
And Tor is ready 9.574
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.921
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.826
Given I shutdown Tails and wait for the computer to power off 4.240
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.357
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.048
And the file system changes introduced in version 6.3~testoverlayfs are present 0.330
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.013
And Tor is ready 11.069
Then the Upgrader considers the system as up-to-date 10.496
# 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.091
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:335 0.931
After features/support/hooks.rb:104 0.046
Tags: @product @automatic_upgrade
19.924
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.493
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
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.020
And Tor is ready 8.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.711
After features/support/hooks.rb:335 0.810
After features/support/hooks.rb:104 0.000