Project Number Date
test_Tails_ISO_21195-dont-include-unused-firmware 3 26 Jul 2026, 02:38

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:37.587 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:8.439
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.450
When I start Tails from USB drive "old" with network unplugged 50.620
Then the boot device has safe access rights 2.638
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.174
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 3.611
After features/support/hooks.rb:108 0.064
Tags: @product
1:27.435
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 53.299
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 25.054
And I take note of which tps features are available 4.241
Then a Tails persistence partition exists on USB drive "old" 0.561
And I shutdown Tails and wait for the computer to power off 3.971
After features/support/hooks.rb:339 0.447
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.661
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.199
Then Tails is running from USB drive "old" 0.237
And all tps features are active 4.832
When I write some files expected to persist 1.321
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 1.962
And I take note of which tps features are available 4.089
And I shutdown Tails and wait for the computer to power off 4.085
# 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" 13.329
After features/support/hooks.rb:339 0.170
After features/support/hooks.rb:108 0.008
Tags: @product
2:11.246
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.147
And I log in to a new session 12.443
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.856
And I plug USB drive "to_upgrade" 2.504
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.233
Then the running Tails is installed on USB drive "to_upgrade" 15.773
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:339 2.402
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.884
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.961
Then all tps features from the old Tails version are active 0.952
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 2.546
And the expected persistent files created with the old Tails version are present in the filesystem 1.118
And all persistent directories from the old Tails version have safe access rights 1.935
After features/support/hooks.rb:339 0.799
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:44.451
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.926
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.016
And Tor is ready 14.447
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.395
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.412
Given I shutdown Tails and wait for the computer to power off 5.472
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.222
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.844
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.211
When the network is plugged 0.020
And Tor is ready 9.697
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.521
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.935
Given I shutdown Tails and wait for the computer to power off 4.079
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.007
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.767
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.014
And Tor is ready 11.150
Then the Upgrader considers the system as up-to-date 10.532
# 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.152
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.347
After features/support/hooks.rb:339 0.959
After features/support/hooks.rb:108 0.037
Tags: @product @automatic_upgrade
21.467
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.324
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.015
And Tor is ready 10.634
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.154
After features/support/hooks.rb:339 0.740
After features/support/hooks.rb:108 0.000