Project Number Date
test_Tails_ISO_21691-gitlab-triage-use-trusted-image 4 23 Jul 2026, 22:22

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 12:2.479 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:18.624
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.562
When I start Tails from USB drive "old" with network unplugged 1:0.157
Then the boot device has safe access rights 2.995
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:339 1.577
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.263
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 55.044
Then Tails is running from USB drive "old" 0.214
And I create a persistent partition 25.214
And I take note of which tps features are available 4.037
Then a Tails persistence partition exists on USB drive "old" 0.563
And I shutdown Tails and wait for the computer to power off 4.140
After features/support/hooks.rb:339 0.611
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.885
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.147
Then Tails is running from USB drive "old" 0.316
And all tps features are active 5.408
When I write some files expected to persist 1.360
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.311
And all persistent directories from the old Tails version have safe access rights 2.020
And I take note of which tps features are available 3.727
And I shutdown Tails and wait for the computer to power off 3.938
# 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.392
After features/support/hooks.rb:339 0.483
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.989
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.040
And I log in to a new session 15.389
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.672
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.874
Then the running Tails is installed on USB drive "to_upgrade" 14.475
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.169
After features/support/hooks.rb:339 2.394
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.638
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.359
Then all tps features from the old Tails version are active 1.024
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.646
And the expected persistent files created with the old Tails version are present in the filesystem 1.189
And all persistent directories from the old Tails version have safe access rights 2.079
After features/support/hooks.rb:339 0.682
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:50.266
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.444
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.018
And Tor is ready 13.358
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.742
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.443
Given I shutdown Tails and wait for the computer to power off 6.925
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.790
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.178
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.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.190
When the network is plugged 0.020
And Tor is ready 11.023
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.889
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.592
Given I shutdown Tails and wait for the computer to power off 3.986
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.906
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.484
And the file system changes introduced in version 6.3~testoverlayfs are present 0.414
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.020
And Tor is ready 9.753
Then the Upgrader considers the system as up-to-date 10.576
# 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.349
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.351
After features/support/hooks.rb:339 0.741
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.812
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.262
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.189
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.021
After features/support/hooks.rb:339 0.921
After features/support/hooks.rb:108 0.000