Project Number Date
test_Tails_ISO_21565-flatpak-safe 6 21 Aug 2026, 16:15

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:22.957 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:21.701
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 14.032
When I start Tails from USB drive "old" with network unplugged 1:3.239
Then the boot device has safe access rights 2.632
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.173
After features/support/hooks.rb:339 1.749
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.879
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 49.109
Then Tails is running from USB drive "old" 0.450
And I create a persistent partition 24.676
And I take note of which tps features are available 7.667
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 5.368
After features/support/hooks.rb:339 0.487
After features/support/hooks.rb:108 0.005
Tags: @product
1:40.022
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.610
Then Tails is running from USB drive "old" 0.308
And all tps features are active 7.897
When I write some files expected to persist 1.300
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 1.689
And I take note of which tps features are available 7.492
And I shutdown Tails and wait for the computer to power off 2.700
# 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.425
After features/support/hooks.rb:339 0.454
After features/support/hooks.rb:108 0.006
Tags: @product
2:26.887
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 22.397
And I log in to a new session 12.189
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.757
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.316
Then the running Tails is installed on USB drive "to_upgrade" 17.785
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 2.271
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.599
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.938
Then all tps features from the old Tails version are active 1.170
And Tails is running from USB drive "to_upgrade" 0.194
And the boot device has safe access rights 2.306
And the expected persistent files created with the old Tails version are present in the filesystem 1.086
And all persistent directories from the old Tails version have safe access rights 1.817
After features/support/hooks.rb:339 0.579
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
3:40.309
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.516
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.034
And Tor is ready 11.990
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.665
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.551
Given I shutdown Tails and wait for the computer to power off 5.489
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.294
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.261
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.110
# 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.209
When the network is plugged 0.036
And Tor is ready 10.338
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.355
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.693
Given I shutdown Tails and wait for the computer to power off 3.960
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.439
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.991
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.029
And Tor is ready 10.550
Then the Upgrader considers the system as up-to-date 0.126
# 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.213
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.425
After features/support/hooks.rb:339 1.043
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
33.558
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 21.499
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
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.761
And Tor is ready 9.261
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.668
After features/support/hooks.rb:339 0.641
After features/support/hooks.rb:108 0.000