Project Number Date
test_Tails_ISO_21664-21666-mitigations 1 29 Jun 2026, 15:28

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 13:9.315 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:29.001
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.145
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.084
And I write an old version of the Tails USB image to disk "old" 15.015
When I start Tails from USB drive "old" with network unplugged 1:9.189
Then the boot device has safe access rights 2.746
And Tails is running from USB drive "old" 0.258
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 3.623
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.282
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 59.540
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 27.034
And I take note of which tps features are available 5.815
Then a Tails persistence partition exists on USB drive "old" 0.599
And I shutdown Tails and wait for the computer to power off 6.964
After features/support/hooks.rb:339 0.595
After features/support/hooks.rb:108 0.007
Tags: @product
1:46.582
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.329
Then Tails is running from USB drive "old" 0.357
And all tps features are active 5.362
When I write some files expected to persist 1.265
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.308
And all persistent directories from the old Tails version have safe access rights 2.173
And I take note of which tps features are available 4.732
And I shutdown Tails and wait for the computer to power off 6.951
# 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.852
After features/support/hooks.rb:339 0.285
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.345
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 without a persistent partition and stopped at Tails Greeter's login screen 9.606
And I log in to a new session 15.116
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.009
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.375
Then the running Tails is installed on USB drive "to_upgrade" 16.635
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:339 2.538
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.985
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.913
Then all tps features from the old Tails version are active 1.129
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.907
And the expected persistent files created with the old Tails version are present in the filesystem 1.172
And all persistent directories from the old Tails version have safe access rights 2.508
After features/support/hooks.rb:339 0.867
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
4:13.895
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 9.045
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.384
When the network is plugged 0.018
And Tor is ready 13.344
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.932
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.336
Given I shutdown Tails and wait for the computer to power off 10.189
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.214
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 6.185
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.175
# 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.209
When the network is plugged 0.021
And Tor is ready 10.225
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.896
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.433
Given I shutdown Tails and wait for the computer to power off 8.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.172
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.844
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.020
And Tor is ready 10.469
Then the Upgrader considers the system as up-to-date 10.555
# 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 4.352
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.439
After features/support/hooks.rb:339 1.105
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
21.222
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.916
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.825
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.056
After features/support/hooks.rb:339 1.078
After features/support/hooks.rb:108 0.000