Project Number Date
test_Tails_ISO_21559-flatpak-locale-tests 4 01 Sep 2026, 20:18

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:31.012 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:29.609
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.125
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 14.710
When I start Tails from USB drive "old" with network unplugged 1:10.131
Then the boot device has safe access rights 2.913
And Tails is running from USB drive "old" 0.266
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 3.447
After features/support/hooks.rb:108 0.060
Tags: @product
1:30.834
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 "old" with network unplugged and I login 51.354
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 25.354
And I take note of which tps features are available 9.234
Then a Tails persistence partition exists on USB drive "old" 0.608
And I shutdown Tails and wait for the computer to power off 3.927
After features/support/hooks.rb:339 0.563
After features/support/hooks.rb:108 0.005
Tags: @product
1:42.895
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 1:8.024
Then Tails is running from USB drive "old" 0.257
And all tps features are active 7.846
When I write some files expected to persist 1.146
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.269
And all persistent directories from the old Tails version have safe access rights 2.122
And I take note of which tps features are available 6.600
And I shutdown Tails and wait for the computer to power off 4.221
# 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" 12.152
After features/support/hooks.rb:339 0.449
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.555
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 9.070
And I log in to a new session 12.824
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.887
And I plug USB drive "to_upgrade" 2.356
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.993
Then the running Tails is installed on USB drive "to_upgrade" 20.115
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:339 3.645
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.564
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.108
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.200
Then all tps features from the old Tails version are active 1.075
And Tails is running from USB drive "to_upgrade" 0.186
And the boot device has safe access rights 2.269
And the expected persistent files created with the old Tails version are present in the filesystem 1.090
And all persistent directories from the old Tails version have safe access rights 1.632
After features/support/hooks.rb:339 0.686
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:56.768
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.364
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
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.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.029
And Tor is ready 13.948
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.158
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.755
Given I shutdown Tails and wait for the computer to power off 5.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.396
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.298
And the file system changes introduced in version 6.2~testoverlayfs are present 0.186
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.109
# 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.189
When the network is plugged 0.035
And Tor is ready 11.122
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.128
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.677
Given I shutdown Tails and wait for the computer to power off 4.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.469
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 9.414
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.037
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.025
And Tor is ready 11.025
Then the Upgrader considers the system as up-to-date 10.493
# 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.306
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.430
After features/support/hooks.rb:339 0.840
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
19.784
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.873
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.046
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.036
And Tor is ready 8.383
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.192
After features/support/hooks.rb:339 0.952
After features/support/hooks.rb:108 0.000