Project Number Date
test_Tails_ISO_stable-flatpak 28 26 Sep 2026, 20:07

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 10:55.041 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:0.342
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.034
When I start Tails from USB drive "old" with network unplugged 43.976
Then the boot device has safe access rights 1.662
And Tails is running from USB drive "old" 0.192
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.034
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 2.009
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.576
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 47.778
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 22.973
And I take note of which tps features are available 6.052
Then a Tails persistence partition exists on USB drive "old" 0.460
And I shutdown Tails and wait for the computer to power off 3.957
After features/support/hooks.rb:339 0.253
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.843
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.278
Then Tails is running from USB drive "old" 0.221
And all tps features are active 6.918
When I write some files expected to persist 1.252
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.109
And all persistence configuration files have safe access rights 0.197
And all persistent directories from the old Tails version have safe access rights 1.532
And I take note of which tps features are available 5.512
And I shutdown Tails and wait for the computer to power off 2.688
# 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.055
After features/support/hooks.rb:339 0.426
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.715
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.200
And I log in to a new session 11.611
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.659
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.733
Then the running Tails is installed on USB drive "to_upgrade" 17.041
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.773
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.370
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.430
Then all tps features from the old Tails version are active 1.147
And Tails is running from USB drive "to_upgrade" 0.168
And the boot device has safe access rights 1.820
And the expected persistent files created with the old Tails version are present in the filesystem 0.982
And all persistent directories from the old Tails version have safe access rights 1.745
After features/support/hooks.rb:339 0.743
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:26.905
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.194
And no SquashFS delta is installed 0.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
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.265
When the network is plugged 0.035
And Tor is ready 12.317
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.546
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.844
Given I shutdown Tails and wait for the computer to power off 5.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.951
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.192
And the file system changes introduced in version 6.2~testoverlayfs are present 0.139
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.107
# 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.165
When the network is plugged 0.026
And Tor is ready 10.093
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.916
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.793
Given I shutdown Tails and wait for the computer to power off 4.067
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.631
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.804
And the file system changes introduced in version 6.3~testoverlayfs are present 0.313
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.153
When the network is plugged 0.030
And Tor is ready 10.045
Then the Upgrader considers the system as up-to-date 0.141
# 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.664
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:339 1.005
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
19.287
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.791
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.499
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.665
After features/support/hooks.rb:339 1.256
After features/support/hooks.rb:108 0.000