Project Number Date
test_Tails_ISO_21565-flatpak-safe 107 28 Oct 2026, 19:20

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:57.469 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:12.454
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 14.250
When I start Tails from USB drive "old" with network unplugged 53.724
Then the boot device has safe access rights 2.611
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 3.633
After features/support/hooks.rb:108 0.041
Tags: @product
1:29.052
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 51.234
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 25.524
And I take note of which tps features are available 7.133
Then a Tails persistence partition exists on USB drive "old" 0.615
And I shutdown Tails and wait for the computer to power off 4.202
After features/support/hooks.rb:339 0.275
After features/support/hooks.rb:108 0.009
Tags: @product
1:40.055
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.460
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.216
Then Tails is running from USB drive "old" 0.229
And all tps features are active 8.086
When I write some files expected to persist 1.272
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.358
And all persistent directories from the old Tails version have safe access rights 1.944
And I take note of which tps features are available 6.330
And I shutdown Tails and wait for the computer to power off 3.983
# 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.004
After features/support/hooks.rb:339 0.300
After features/support/hooks.rb:108 0.009
Tags: @product
2:15.781
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.996
And I log in to a new session 12.670
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.798
And I plug USB drive "to_upgrade" 2.338
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.606
Then the running Tails is installed on USB drive "to_upgrade" 19.095
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 4.601
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.414
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.293
Then all tps features from the old Tails version are active 1.162
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 2.580
And the expected persistent files created with the old Tails version are present in the filesystem 1.164
And all persistent directories from the old Tails version have safe access rights 1.813
After features/support/hooks.rb:339 0.799
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
3:46.999
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.394
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.045
And Tor is ready 13.417
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.312
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.485
Given I shutdown Tails and wait for the computer to power off 6.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.762
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.466
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.169
When the network is plugged 0.032
And Tor is ready 11.036
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.005
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.260
Given I shutdown Tails and wait for the computer to power off 4.538
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.508
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 10.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
And only the 6.3~testoverlayfs SquashFS delta is installed 0.027
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.029
And Tor is ready 10.907
Then the Upgrader considers the system as up-to-date 0.084
# 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 3.260
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.366
After features/support/hooks.rb:339 0.870
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
19.712
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 10.116
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.011
After features/support/hooks.rb:339 1.033
After features/support/hooks.rb:108 0.000