Project Number Date
test_Tails_ISO_21866-update-firmware-sof 1 03 Nov 2026, 14: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:22.724 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:14.696
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.710
When I start Tails from USB drive "old" with network unplugged 57.244
Then the boot device has safe access rights 1.992
And Tails is running from USB drive "old" 0.195
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.025
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 3.380
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.506
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 48.733
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 23.995
And I take note of which tps features are available 6.264
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 2.534
After features/support/hooks.rb:339 0.324
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.297
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.666
Then Tails is running from USB drive "old" 0.219
And all tps features are active 7.751
When I write some files expected to persist 1.186
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.113
And all persistence configuration files have safe access rights 0.233
And all persistent directories from the old Tails version have safe access rights 1.847
And I take note of which tps features are available 6.316
And I shutdown Tails and wait for the computer to power off 4.038
# 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.839
After features/support/hooks.rb:339 0.505
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.673
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.406
And I log in to a new session 12.519
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.628
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.746
Then the running Tails is installed on USB drive "to_upgrade" 18.894
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 3.452
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.281
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.985
Then all tps features from the old Tails version are active 1.284
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.146
And the expected persistent files created with the old Tails version are present in the filesystem 0.862
And all persistent directories from the old Tails version have safe access rights 1.659
After features/support/hooks.rb:339 0.961
After features/support/hooks.rb:108 0.057
Tags: @product @automatic_upgrade
3:28.138
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 8.196
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.027
And Tor is ready 11.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.886
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.397
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.209
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 9.624
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.110
# 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.201
When the network is plugged 0.034
And Tor is ready 10.253
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.319
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.420
Given I shutdown Tails and wait for the computer to power off 2.697
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.769
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.960
And the file system changes introduced in version 6.3~testoverlayfs are present 0.322
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.111
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.137
When the network is plugged 0.035
And Tor is ready 10.414
Then the Upgrader considers the system as up-to-date 0.117
# 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.665
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 0.711
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
20.131
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.948
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 11.526
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.321
After features/support/hooks.rb:339 0.554
After features/support/hooks.rb:108 0.000