Project Number Date
test_Tails_ISO_21565-flatpak-safe 108 28 Oct 2026, 19:37

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:0.855 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:15.402
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.104
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 14.396
When I start Tails from USB drive "old" with network unplugged 56.670
Then the boot device has safe access rights 2.514
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 1.240
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.690
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login 53.062
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 24.252
And I take note of which tps features are available 8.937
Then a Tails persistence partition exists on USB drive "old" 0.778
And I shutdown Tails and wait for the computer to power off 4.306
After features/support/hooks.rb:339 0.272
After features/support/hooks.rb:108 0.007
Tags: @product
1:41.726
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.201
Then Tails is running from USB drive "old" 0.248
And all tps features are active 7.348
When I write some files expected to persist 1.799
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.317
And all persistent directories from the old Tails version have safe access rights 2.260
And I take note of which tps features are available 7.007
And I shutdown Tails and wait for the computer to power off 3.997
# 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" 13.222
After features/support/hooks.rb:339 0.099
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.865
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 without a persistent partition and stopped at Tails Greeter's login screen 8.596
And I log in to a new session 13.069
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.020
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.676
Then the running Tails is installed on USB drive "to_upgrade" 18.991
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.914
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.302
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.126
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.656
Then all tps features from the old Tails version are active 1.114
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.142
And the expected persistent files created with the old Tails version are present in the filesystem 0.927
And all persistent directories from the old Tails version have safe access rights 2.093
After features/support/hooks.rb:339 0.930
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
3:40.964
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.752
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.181
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.325
When the network is plugged 0.027
And Tor is ready 12.727
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.776
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.818
Given I shutdown Tails and wait for the computer to power off 5.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.206
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.427
And the file system changes introduced in version 6.2~testoverlayfs are present 0.161
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.167
When the network is plugged 0.029
And Tor is ready 11.025
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.176
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.992
Given I shutdown Tails and wait for the computer to power off 3.996
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.384
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.656
And the file system changes introduced in version 6.3~testoverlayfs are present 0.403
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.032
And Tor is ready 10.207
Then the Upgrader considers the system as up-to-date 0.077
# 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.733
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.444
After features/support/hooks.rb:339 1.075
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
19.902
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 8.383
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.356
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.792
After features/support/hooks.rb:339 0.807
After features/support/hooks.rb:108 0.000