Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 33 19 May 2026, 19:25

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:5.710 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:19.853
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.987
When I start Tails from USB drive "old" with network unplugged 1:1.141
Then the boot device has safe access rights 2.860
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.204
After features/support/hooks.rb:335 1.467
After features/support/hooks.rb:104 0.007
Tags: @product
1:31.532
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 56.699
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 26.311
And I take note of which tps features are available 0.416
Then a Tails persistence partition exists on USB drive "old" 0.678
And I shutdown Tails and wait for the computer to power off 7.051
After features/support/hooks.rb:335 0.341
After features/support/hooks.rb:104 0.008
Tags: @product
1:30.369
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.128
Then Tails is running from USB drive "old" 0.231
And all tps features are active 1.298
When I write some files expected to persist 1.464
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.385
And all persistent directories from the old Tails version have safe access rights 2.355
And I take note of which tps features are available 0.281
And I shutdown Tails and wait for the computer to power off 7.149
# 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.772
After features/support/hooks.rb:335 0.495
After features/support/hooks.rb:104 0.008
Tags: @product
2:15.942
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.389
And I log in to a new session 14.800
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.796
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.598
Then the running Tails is installed on USB drive "to_upgrade" 16.808
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:335 2.441
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.945
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.450
Then all tps features from the old Tails version are active 1.176
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 2.755
And the expected persistent files created with the old Tails version are present in the filesystem 1.196
And all persistent directories from the old Tails version have safe access rights 1.990
After features/support/hooks.rb:335 0.762
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
3:52.158
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 8.380
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.014
And Tor is ready 13.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.879
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.050
Given I shutdown Tails and wait for the computer to power off 7.065
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.485
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.625
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.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.269
When the network is plugged 0.056
And Tor is ready 11.804
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.698
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.726
Given I shutdown Tails and wait for the computer to power off 8.548
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.975
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.281
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.014
And Tor is ready 10.618
Then the Upgrader considers the system as up-to-date 10.987
# 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.064
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.490
After features/support/hooks.rb:335 1.001
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
21.907
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.934
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 10.862
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.721
After features/support/hooks.rb:335 0.908
After features/support/hooks.rb:104 0.000