Project Number Date
test_Tails_ISO_21565-flatpak-safe 94 20 Oct 2026, 03:16

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:47.521 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:2.900
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.051
When I start Tails from USB drive "old" with network unplugged 46.077
Then the boot device has safe access rights 2.010
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:339 3.632
After features/support/hooks.rb:108 0.043
Tags: @product
1:20.452
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 47.046
Then Tails is running from USB drive "old" 0.171
And I create a persistent partition 22.442
And I take note of which tps features are available 6.164
Then a Tails persistence partition exists on USB drive "old" 0.523
And I shutdown Tails and wait for the computer to power off 4.032
After features/support/hooks.rb:339 0.401
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.272
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.319
Then Tails is running from USB drive "old" 0.202
And all tps features are active 7.010
When I write some files expected to persist 1.053
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.297
And all persistent directories from the old Tails version have safe access rights 1.586
And I take note of which tps features are available 5.793
And I shutdown Tails and wait for the computer to power off 2.529
# 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.197
After features/support/hooks.rb:339 0.550
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.681
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.322
And I log in to a new session 10.199
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.597
And I plug USB drive "to_upgrade" 2.306
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.594
Then the running Tails is installed on USB drive "to_upgrade" 17.381
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:339 1.674
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.038
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 "to_upgrade" with network unplugged and I login with persistence enabled 59.531
Then all tps features from the old Tails version are active 1.016
And Tails is running from USB drive "to_upgrade" 0.181
And the boot device has safe access rights 1.952
And the expected persistent files created with the old Tails version are present in the filesystem 0.876
And all persistent directories from the old Tails version have safe access rights 1.377
After features/support/hooks.rb:339 0.603
After features/support/hooks.rb:108 0.006
3:23.534
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.049
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.172
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.367
When the network is plugged 0.038
And Tor is ready 13.118
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.297
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.018
Given I shutdown Tails and wait for the computer to power off 5.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.213
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.209
And the file system changes introduced in version 6.2~testoverlayfs are present 0.181
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.117
# 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.172
When the network is plugged 0.035
And Tor is ready 11.303
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.306
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.517
Given I shutdown Tails and wait for the computer to power off 3.886
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.070
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.472
And the file system changes introduced in version 6.3~testoverlayfs are present 0.296
And only the 6.3~testoverlayfs SquashFS delta is installed 0.032
# 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.106
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.159
When the network is plugged 0.033
And Tor is ready 10.256
Then the Upgrader considers the system as up-to-date 0.083
# 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 2.974
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.323
After features/support/hooks.rb:339 0.734
After features/support/hooks.rb:108 0.023
17.642
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.878
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.292
After features/support/hooks.rb:339 0.504
After features/support/hooks.rb:108 0.000