Project Number Date
test_Tails_ISO_21811-firmware-sof-2026.09.1-1 1 06 Oct 2026, 16:04

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:51.420 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:22.096
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 13.666
When I start Tails from USB drive "old" with network unplugged 1:3.950
Then the boot device has safe access rights 2.542
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.188
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.517
After features/support/hooks.rb:108 0.022
Tags: @product
1:27.749
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 49.134
Then Tails is running from USB drive "old" 0.260
And I create a persistent partition 25.285
And I take note of which tps features are available 7.247
Then a Tails persistence partition exists on USB drive "old" 0.586
And I shutdown Tails and wait for the computer to power off 5.143
After features/support/hooks.rb:339 0.613
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.965
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.171
Then Tails is running from USB drive "old" 0.213
And all tps features are active 7.822
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.726
And I take note of which tps features are available 6.316
And I shutdown Tails and wait for the computer to power off 2.613
# 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.289
After features/support/hooks.rb:339 0.368
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.282
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.401
And I log in to a new session 12.017
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.699
And I plug USB drive "to_upgrade" 2.301
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.363
Then the running Tails is installed on USB drive "to_upgrade" 18.246
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 2.111
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.651
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.217
Then all tps features from the old Tails version are active 1.097
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.464
And the expected persistent files created with the old Tails version are present in the filesystem 0.994
And all persistent directories from the old Tails version have safe access rights 1.588
After features/support/hooks.rb:339 0.526
After features/support/hooks.rb:108 0.005
3:41.427
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.899
And no SquashFS delta is installed 0.068
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.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.329
When the network is plugged 0.028
And Tor is ready 13.628
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.972
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.528
Given I shutdown Tails and wait for the computer to power off 5.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.378
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.604
And the file system changes introduced in version 6.2~testoverlayfs are present 0.176
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.192
When the network is plugged 0.026
And Tor is ready 10.429
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.018
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.448
Given I shutdown Tails and wait for the computer to power off 4.219
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.974
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.977
And the file system changes introduced in version 6.3~testoverlayfs are present 0.371
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.170
When the network is plugged 0.032
And Tor is ready 10.318
Then the Upgrader considers the system as up-to-date 0.150
# 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.845
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.459
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.033
18.248
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.880
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 8.512
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.508
After features/support/hooks.rb:339 0.966
After features/support/hooks.rb:108 0.000