Project Number Date
test_Tails_ISO_stable-flatpak 38 06 Oct 2026, 19:53

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:56.511 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.864
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.485
When I start Tails from USB drive "old" with network unplugged 53.023
Then the boot device has safe access rights 2.457
And Tails is running from USB drive "old" 0.267
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.686
After features/support/hooks.rb:108 0.017
Tags: @product
1:28.384
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 50.462
Then Tails is running from USB drive "old" 0.189
And I create a persistent partition 24.806
And I take note of which tps features are available 6.906
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 5.371
After features/support/hooks.rb:339 0.456
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.931
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.120
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.408
Then Tails is running from USB drive "old" 0.201
And all tps features are active 8.359
When I write some files expected to persist 1.455
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.286
And all persistent directories from the old Tails version have safe access rights 2.031
And I take note of which tps features are available 7.082
And I shutdown Tails and wait for the computer to power off 4.173
# 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.615
After features/support/hooks.rb:339 0.414
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.178
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.816
And I log in to a new session 11.823
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.688
And I plug USB drive "to_upgrade" 2.377
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.442
Then the running Tails is installed on USB drive "to_upgrade" 17.784
And I unplug USB drive "to_upgrade" 0.112
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 1.934
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.156
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.114
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.375
Then all tps features from the old Tails version are active 1.561
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.397
And the expected persistent files created with the old Tails version are present in the filesystem 1.373
And all persistent directories from the old Tails version have safe access rights 2.083
After features/support/hooks.rb:339 0.633
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
3:47.837
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.225
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.499
When the network is plugged 0.046
And Tor is ready 13.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.083
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.336
Given I shutdown Tails and wait for the computer to power off 6.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.247
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.594
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
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.112
# 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.212
When the network is plugged 0.030
And Tor is ready 9.964
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.961
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.086
Given I shutdown Tails and wait for the computer to power off 4.199
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.163
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.615
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.033
And Tor is ready 11.065
Then the Upgrader considers the system as up-to-date 0.104
# 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.831
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.384
After features/support/hooks.rb:339 1.086
After features/support/hooks.rb:108 0.024
Tags: @product @automatic_upgrade
21.159
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 8.426
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 10.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.301
After features/support/hooks.rb:339 0.655
After features/support/hooks.rb:108 0.000