Project Number Date
test_Tails_ISO_21565-flatpak-safe 126 05 Nov 2026, 12:34

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:25.784 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:25.304
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.676
When I start Tails from USB drive "old" with network unplugged 1:7.868
Then the boot device has safe access rights 1.998
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 1.300
After features/support/hooks.rb:108 0.008
Tags: @product
1:19.712
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 47.430
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 22.827
And I take note of which tps features are available 5.898
Then a Tails persistence partition exists on USB drive "old" 0.516
And I shutdown Tails and wait for the computer to power off 2.583
After features/support/hooks.rb:339 0.141
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.707
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.865
Then Tails is running from USB drive "old" 0.181
And all tps features are active 7.818
When I write some files expected to persist 1.240
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.228
And all persistent directories from the old Tails version have safe access rights 1.640
And I take note of which tps features are available 6.185
And I shutdown Tails and wait for the computer to power off 2.627
# 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.619
After features/support/hooks.rb:339 0.105
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.766
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.358
And I log in to a new session 12.110
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.701
And I plug USB drive "to_upgrade" 2.190
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.596
Then the running Tails is installed on USB drive "to_upgrade" 18.589
And I unplug USB drive "to_upgrade" 0.111
And I unplug USB drive "__internal" 0.107
After features/support/hooks.rb:339 1.708
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.290
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.509
Then all tps features from the old Tails version are active 1.002
And Tails is running from USB drive "to_upgrade" 0.166
And the boot device has safe access rights 2.131
And the expected persistent files created with the old Tails version are present in the filesystem 0.882
And all persistent directories from the old Tails version have safe access rights 1.522
After features/support/hooks.rb:339 0.863
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
3:28.597
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.910
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.386
When the network is plugged 0.040
And Tor is ready 12.673
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.902
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.989
Given I shutdown Tails and wait for the computer to power off 5.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.626
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.416
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.157
When the network is plugged 0.101
And Tor is ready 10.413
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.972
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.669
Given I shutdown Tails and wait for the computer to power off 3.962
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.853
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.678
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
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.101
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.031
And Tor is ready 9.980
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.143
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.475
After features/support/hooks.rb:339 0.666
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
19.406
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.030
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.051
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 10.393
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.619
After features/support/hooks.rb:339 0.766
After features/support/hooks.rb:108 0.000