Project Number Date
test_Tails_ISO_21559-flatpak-locale-tests 5 01 Sep 2026, 20:52

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:58.177 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:23.528
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.315
When I start Tails from USB drive "old" with network unplugged 1:4.989
Then the boot device has safe access rights 2.442
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.106
After features/support/hooks.rb:339 1.286
After features/support/hooks.rb:108 0.008
Tags: @product
1:26.417
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 50.619
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 24.008
And I take note of which tps features are available 6.746
Then a Tails persistence partition exists on USB drive "old" 0.472
And I shutdown Tails and wait for the computer to power off 4.163
After features/support/hooks.rb:339 0.441
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.682
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.116
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.724
Then Tails is running from USB drive "old" 0.302
And all tps features are active 8.281
When I write some files expected to persist 1.350
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.866
And I take note of which tps features are available 6.729
And I shutdown Tails and wait for the computer to power off 4.197
# 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.658
After features/support/hooks.rb:339 0.212
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.102
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.045
And I log in to a new session 11.494
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.851
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.310
Then the running Tails is installed on USB drive "to_upgrade" 19.915
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 3.721
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.676
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.767
Then all tps features from the old Tails version are active 1.309
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.492
And the expected persistent files created with the old Tails version are present in the filesystem 1.036
And all persistent directories from the old Tails version have safe access rights 1.730
After features/support/hooks.rb:339 0.569
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
3:41.670
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.430
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.328
When the network is plugged 0.025
And Tor is ready 12.714
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.090
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.849
Given I shutdown Tails and wait for the computer to power off 5.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.567
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.154
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.124
# 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.198
When the network is plugged 0.040
And Tor is ready 10.974
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.913
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.880
Given I shutdown Tails and wait for the computer to power off 3.981
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.671
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 9.028
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.027
And Tor is ready 11.127
Then the Upgrader considers the system as up-to-date 0.090
# 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.868
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:339 0.692
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.099
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 7.843
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.207
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.545
After features/support/hooks.rb:339 0.575
After features/support/hooks.rb:108 0.000