Project Number Date
test_Tails_ISO_21565-flatpak-safe 75 06 Oct 2026, 19:39

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:51.764 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:10.475
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.125
When I start Tails from USB drive "old" with network unplugged 53.260
Then the boot device has safe access rights 2.405
And Tails is running from USB drive "old" 0.180
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.589
After features/support/hooks.rb:108 0.021
Tags: @product
1:23.575
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 48.241
Then Tails is running from USB drive "old" 0.273
And I create a persistent partition 23.351
And I take note of which tps features are available 7.096
Then a Tails persistence partition exists on USB drive "old" 0.547
And I shutdown Tails and wait for the computer to power off 3.982
After features/support/hooks.rb:339 0.270
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.584
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.440
Then Tails is running from USB drive "old" 0.329
And all tps features are active 8.058
When I write some files expected to persist 1.207
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 1.691
And I take note of which tps features are available 6.486
And I shutdown Tails and wait for the computer to power off 4.059
# 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.723
After features/support/hooks.rb:339 0.231
After features/support/hooks.rb:108 0.007
Tags: @product
2:16.808
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.784
And I log in to a new session 14.095
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.794
And I plug USB drive "to_upgrade" 2.250
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.075
Then the running Tails is installed on USB drive "to_upgrade" 19.333
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.350
After features/support/hooks.rb:339 1.885
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.822
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.834
Then all tps features from the old Tails version are active 1.121
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.484
And the expected persistent files created with the old Tails version are present in the filesystem 1.028
And all persistent directories from the old Tails version have safe access rights 2.065
After features/support/hooks.rb:339 0.889
After features/support/hooks.rb:108 0.010
3:52.064
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.227
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.039
And Tor is ready 13.372
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.031
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.503
Given I shutdown Tails and wait for the computer to power off 5.382
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.600
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.874
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.104
# 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.170
When the network is plugged 0.026
And Tor is ready 11.153
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.193
Given I shutdown Tails and wait for the computer to power off 4.210
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.013
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.959
And the file system changes introduced in version 6.3~testoverlayfs are present 0.419
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.023
And Tor is ready 10.594
Then the Upgrader considers the system as up-to-date 0.117
# 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.679
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.360
After features/support/hooks.rb:339 0.860
After features/support/hooks.rb:108 0.010
19.433
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.710
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 10.082
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.309
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.000