Project Number Date
test_Tails_ISO_stable-flatpak 24 21 Sep 2026, 19:42

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:7.573 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:12.144
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.018
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 12.942
When I start Tails from USB drive "old" with network unplugged 55.841
Then the boot device has safe access rights 1.719
And Tails is running from USB drive "old" 0.162
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.384
After features/support/hooks.rb:108 0.016
Tags: @product
1:21.003
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login 48.155
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 23.650
And I take note of which tps features are available 5.841
Then a Tails persistence partition exists on USB drive "old" 0.452
And I shutdown Tails and wait for the computer to power off 2.582
After features/support/hooks.rb:339 0.381
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.750
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.338
Then Tails is running from USB drive "old" 0.201
And all tps features are active 7.149
When I write some files expected to persist 1.243
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.202
And all persistent directories from the old Tails version have safe access rights 1.648
And I take note of which tps features are available 5.806
And I shutdown Tails and wait for the computer to power off 2.519
# 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.405
After features/support/hooks.rb:339 0.580
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.452
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.067
And I log in to a new session 11.025
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.589
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.155
Then the running Tails is installed on USB drive "to_upgrade" 17.166
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 2.065
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.792
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.726
Then all tps features from the old Tails version are active 1.024
And Tails is running from USB drive "to_upgrade" 0.214
And the boot device has safe access rights 1.992
And the expected persistent files created with the old Tails version are present in the filesystem 1.017
And all persistent directories from the old Tails version have safe access rights 1.739
After features/support/hooks.rb:339 0.844
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
3:27.648
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.826
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.156
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.323
When the network is plugged 0.042
And Tor is ready 13.688
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.678
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.165
Given I shutdown Tails and wait for the computer to power off 5.240
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.942
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.475
And the file system changes introduced in version 6.2~testoverlayfs are present 0.151
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.162
When the network is plugged 0.033
And Tor is ready 10.394
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.708
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.009
Given I shutdown Tails and wait for the computer to power off 2.575
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.807
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.718
And the file system changes introduced in version 6.3~testoverlayfs are present 0.324
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.027
And Tor is ready 10.431
Then the Upgrader considers the system as up-to-date 0.085
# 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.513
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.288
After features/support/hooks.rb:339 0.685
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.781
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.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.749
After features/support/hooks.rb:339 1.129
After features/support/hooks.rb:108 0.000