Project Number Date
test_Tails_ISO_21866-update-firmware-sof 2 03 Nov 2026, 20:36

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:30.885 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:6.258
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.404
When I start Tails from USB drive "old" with network unplugged 48.258
Then the boot device has safe access rights 2.735
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.310
After features/support/hooks.rb:108 0.018
Tags: @product
1:24.962
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 49.423
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 23.872
And I take note of which tps features are available 6.629
Then a Tails persistence partition exists on USB drive "old" 0.538
And I shutdown Tails and wait for the computer to power off 4.124
After features/support/hooks.rb:339 0.353
After features/support/hooks.rb:108 0.005
Tags: @product
1:38.641
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.220
Then Tails is running from USB drive "old" 0.216
And all tps features are active 8.269
When I write some files expected to persist 1.295
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.623
And I take note of which tps features are available 6.288
And I shutdown Tails and wait for the computer to power off 4.223
# 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.967
After features/support/hooks.rb:339 0.181
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.013
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.896
And I log in to a new session 13.476
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.716
And I plug USB drive "to_upgrade" 2.350
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.829
Then the running Tails is installed on USB drive "to_upgrade" 19.527
And I unplug USB drive "to_upgrade" 0.109
And I unplug USB drive "__internal" 0.108
After features/support/hooks.rb:339 3.652
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.885
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.114
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.012
Then all tps features from the old Tails version are active 1.260
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.497
And the expected persistent files created with the old Tails version are present in the filesystem 1.011
And all persistent directories from the old Tails version have safe access rights 1.746
After features/support/hooks.rb:339 0.773
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
3:33.821
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.295
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.305
When the network is plugged 0.026
And Tor is ready 12.064
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.946
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.453
Given I shutdown Tails and wait for the computer to power off 5.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.185
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 8.165
And the file system changes introduced in version 6.2~testoverlayfs are present 0.251
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.218
When the network is plugged 0.031
And Tor is ready 10.512
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.585
Given I shutdown Tails and wait for the computer to power off 4.090
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.234
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.952
And the file system changes introduced in version 6.3~testoverlayfs are present 0.301
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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.033
And Tor is ready 10.326
Then the Upgrader considers the system as up-to-date 0.096
# 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.602
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.327
After features/support/hooks.rb:339 1.004
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.302
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.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.833
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.964
After features/support/hooks.rb:339 0.845
After features/support/hooks.rb:108 0.000