Project Number Date
test_Tails_ISO_21565-flatpak-safe 133 09 Nov 2026, 20:44

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 10:51.447 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:6.551
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.362
When I start Tails from USB drive "old" with network unplugged 49.815
Then the boot device has safe access rights 1.760
And Tails is running from USB drive "old" 0.186
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.133
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 3.445
After features/support/hooks.rb:108 0.004
Tags: @product
1:21.482
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 48.285
Then Tails is running from USB drive "old" 0.213
And I create a persistent partition 22.766
And I take note of which tps features are available 5.785
Then a Tails persistence partition exists on USB drive "old" 0.435
And I shutdown Tails and wait for the computer to power off 3.893
After features/support/hooks.rb:339 0.361
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.525
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.038
Then Tails is running from USB drive "old" 0.186
And all tps features are active 6.880
When I write some files expected to persist 1.049
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.125
And all persistence configuration files have safe access rights 0.212
And all persistent directories from the old Tails version have safe access rights 1.444
And I take note of which tps features are available 5.685
And I shutdown Tails and wait for the computer to power off 2.506
# 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.313
After features/support/hooks.rb:339 0.310
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.011
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 without a persistent partition and stopped at Tails Greeter's login screen 8.411
And I log in to a new session 11.007
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.597
And I plug USB drive "to_upgrade" 2.616
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.177
Then the running Tails is installed on USB drive "to_upgrade" 17.959
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.639
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.561
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.360
Then all tps features from the old Tails version are active 0.998
And Tails is running from USB drive "to_upgrade" 0.179
And the boot device has safe access rights 1.778
And the expected persistent files created with the old Tails version are present in the filesystem 0.786
And all persistent directories from the old Tails version have safe access rights 1.361
After features/support/hooks.rb:339 0.611
After features/support/hooks.rb:108 0.005
3:21.039
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.096
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.029
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.153
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.264
When the network is plugged 0.025
And Tor is ready 11.651
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.934
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.228
Given I shutdown Tails and wait for the computer to power off 5.220
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.327
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.522
And the file system changes introduced in version 6.2~testoverlayfs are present 0.136
And only the 6.2~testoverlayfs SquashFS delta is installed 0.022
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.182
When the network is plugged 0.022
And Tor is ready 9.973
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.466
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.541
Given I shutdown Tails and wait for the computer to power off 4.082
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.093
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.277
And the file system changes introduced in version 6.3~testoverlayfs are present 0.282
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.145
When the network is plugged 0.033
And Tor is ready 10.239
Then the Upgrader considers the system as up-to-date 0.076
# 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.107
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 0.812
After features/support/hooks.rb:108 0.008
18.275
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 7.774
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
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.028
And Tor is ready 7.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.472
After features/support/hooks.rb:339 0.871
After features/support/hooks.rb:108 0.000