Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 19 12 May 2026, 13:02

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:47.855 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:25.288
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.199
When I start Tails from USB drive "old" with network unplugged 1:6.230
Then the boot device has safe access rights 2.805
And Tails is running from USB drive "old" 0.405
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.227
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:335 1.551
After features/support/hooks.rb:104 0.007
Tags: @product
1:25.274
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 54.493
Then Tails is running from USB drive "old" 0.264
And I create a persistent partition 25.008
And I take note of which tps features are available 0.786
Then a Tails persistence partition exists on USB drive "old" 0.607
And I shutdown Tails and wait for the computer to power off 4.049
After features/support/hooks.rb:335 0.600
After features/support/hooks.rb:104 0.008
Tags: @product
1:29.045
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.091
Then Tails is running from USB drive "old" 0.317
And all tps features are active 1.186
When I write some files expected to persist 1.331
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.482
And all persistent directories from the old Tails version have safe access rights 2.057
And I take note of which tps features are available 0.258
And I shutdown Tails and wait for the computer to power off 8.317
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.747
After features/support/hooks.rb:335 0.326
After features/support/hooks.rb:104 0.006
Tags: @product
2:12.289
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.953
And I log in to a new session 12.146
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.854
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.088
Then the running Tails is installed on USB drive "to_upgrade" 16.727
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:335 2.139
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.387
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.602
Then all tps features from the old Tails version are active 1.168
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.793
And the expected persistent files created with the old Tails version are present in the filesystem 1.135
And all persistent directories from the old Tails version have safe access rights 2.406
After features/support/hooks.rb:335 0.902
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
4:34.848
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.415
And no SquashFS delta is installed 0.067
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.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.021
And Tor is ready 21.372
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.375
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.748
Given I shutdown Tails and wait for the computer to power off 20.225
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.234
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.152
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# 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.211
When the network is plugged 0.014
And Tor is ready 21.526
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.951
Given I shutdown Tails and wait for the computer to power off 13.485
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.468
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.085
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.020
And Tor is ready 21.901
Then the Upgrader considers the system as up-to-date 0.107
# 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.325
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.554
After features/support/hooks.rb:335 1.188
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
28.721
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.120
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 19.837
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.389
After features/support/hooks.rb:335 0.563
After features/support/hooks.rb:104 0.000