Project Number Date
test_Tails_ISO_21691-gitlab-triage-use-trusted-image 2 23 Jul 2026, 17:57

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:54.220 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:9.556
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.650
When I start Tails from USB drive "old" with network unplugged 51.477
Then the boot device has safe access rights 2.581
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:339 3.894
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.843
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 56.407
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 25.106
And I take note of which tps features are available 4.420
Then a Tails persistence partition exists on USB drive "old" 0.571
And I shutdown Tails and wait for the computer to power off 4.022
After features/support/hooks.rb:339 0.551
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.595
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.917
Then Tails is running from USB drive "old" 0.281
And all tps features are active 5.437
When I write some files expected to persist 1.405
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 2.012
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.132
# 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.796
After features/support/hooks.rb:339 0.238
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.666
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 without a persistent partition and stopped at Tails Greeter's login screen 8.220
And I log in to a new session 12.567
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.869
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.777
Then the running Tails is installed on USB drive "to_upgrade" 14.655
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:339 2.499
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.077
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.958
Then all tps features from the old Tails version are active 1.076
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.765
And the expected persistent files created with the old Tails version are present in the filesystem 1.130
And all persistent directories from the old Tails version have safe access rights 1.828
After features/support/hooks.rb:339 0.833
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:52.115
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.474
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.021
And Tor is ready 13.890
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.962
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.441
Given I shutdown Tails and wait for the computer to power off 6.832
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.092
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.303
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.203
When the network is plugged 0.018
And Tor is ready 10.298
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.689
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.205
Given I shutdown Tails and wait for the computer to power off 4.034
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.595
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.477
And the file system changes introduced in version 6.3~testoverlayfs are present 0.392
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.208
When the network is plugged 0.019
And Tor is ready 11.118
Then the Upgrader considers the system as up-to-date 10.545
# 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.253
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:339 0.834
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
20.365
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.360
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 9.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.048
After features/support/hooks.rb:339 0.844
After features/support/hooks.rb:108 0.000