Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 54 08 Jun 2026, 14:32

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:7.942 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:17.081
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.513
When I start Tails from USB drive "old" with network unplugged 57.952
Then the boot device has safe access rights 2.827
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:335 3.482
After features/support/hooks.rb:104 0.043
Tags: @product
1:35.352
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 56.695
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 28.512
And I take note of which tps features are available 0.586
Then a Tails persistence partition exists on USB drive "old" 0.827
And I shutdown Tails and wait for the computer to power off 8.431
After features/support/hooks.rb:335 0.504
After features/support/hooks.rb:104 0.008
Tags: @product
1:27.527
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.397
Then Tails is running from USB drive "old" 0.204
And all tps features are active 1.269
When I write some files expected to persist 1.277
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.310
And all persistent directories from the old Tails version have safe access rights 2.223
And I take note of which tps features are available 0.174
And I shutdown Tails and wait for the computer to power off 4.170
# 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.287
After features/support/hooks.rb:335 0.311
After features/support/hooks.rb:104 0.008
Tags: @product
2:16.042
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.998
And I log in to a new session 13.797
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.026
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.618
Then the running Tails is installed on USB drive "to_upgrade" 17.060
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:335 2.518
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.866
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.142
Then all tps features from the old Tails version are active 1.138
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.858
And the expected persistent files created with the old Tails version are present in the filesystem 1.392
And all persistent directories from the old Tails version have safe access rights 2.028
After features/support/hooks.rb:335 0.916
After features/support/hooks.rb:104 0.006
3:55.679
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.381
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.018
And Tor is ready 13.842
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.303
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.839
Given I shutdown Tails and wait for the computer to power off 7.533
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.596
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 1.470
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.203
When the network is plugged 0.020
And Tor is ready 11.705
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.455
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.436
Given I shutdown Tails and wait for the computer to power off 8.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.607
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.366
And the file system changes introduced in version 6.3~testoverlayfs are present 0.662
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.297
When the network is plugged 0.029
And Tor is ready 11.609
Then the Upgrader considers the system as up-to-date 10.675
# 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.050
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.482
After features/support/hooks.rb:335 0.817
After features/support/hooks.rb:104 0.015
20.392
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 with a persistent partition enabled and logged in 7.819
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
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.052
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 10.115
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.099
After features/support/hooks.rb:335 0.840
After features/support/hooks.rb:104 0.000