Project Number Date
test_Tails_ISO_21565-flatpak-safe 73 06 Oct 2026, 13:49

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:55.444 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:7.866
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.090
When I start Tails from USB drive "old" with network unplugged 49.403
Then the boot device has safe access rights 2.608
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.735
After features/support/hooks.rb:108 0.051
Tags: @product
1:27.660
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.113
And I start Tails from USB drive "old" with network unplugged and I login 50.831
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 24.665
And I take note of which tps features are available 7.253
Then a Tails persistence partition exists on USB drive "old" 0.589
And I shutdown Tails and wait for the computer to power off 3.981
After features/support/hooks.rb:339 0.216
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.211
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.116
Then Tails is running from USB drive "old" 0.307
And all tps features are active 8.019
When I write some files expected to persist 1.134
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.327
And all persistent directories from the old Tails version have safe access rights 1.850
And I take note of which tps features are available 8.564
And I shutdown Tails and wait for the computer to power off 3.972
# 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.674
After features/support/hooks.rb:339 0.132
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.993
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.620
And I log in to a new session 13.591
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.784
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.964
Then the running Tails is installed on USB drive "to_upgrade" 19.551
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.117
After features/support/hooks.rb:339 1.827
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.152
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.745
Then all tps features from the old Tails version are active 1.391
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.442
And the expected persistent files created with the old Tails version are present in the filesystem 1.329
And all persistent directories from the old Tails version have safe access rights 1.923
After features/support/hooks.rb:339 0.610
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:50.845
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.744
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.332
When the network is plugged 0.029
And Tor is ready 13.556
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.160
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.884
Given I shutdown Tails and wait for the computer to power off 5.642
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.325
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.364
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
And only the 6.2~testoverlayfs SquashFS delta is installed 0.098
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.184
# 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.431
When the network is plugged 0.037
And Tor is ready 11.316
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.904
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.350
Given I shutdown Tails and wait for the computer to power off 2.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.213
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.395
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.027
And Tor is ready 10.607
Then the Upgrader considers the system as up-to-date 0.112
# 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.577
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 0.994
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
19.714
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.413
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.335
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.865
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.955
After features/support/hooks.rb:339 1.022
After features/support/hooks.rb:108 0.000