Project Number Date
test_Tails_ISO_21691-gitlab-triage-use-trusted-image 7 26 Jul 2026, 21:24

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:22.447 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:16.315
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.090
When I start Tails from USB drive "old" with network unplugged 57.484
Then the boot device has safe access rights 2.922
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:339 1.750
After features/support/hooks.rb:108 0.009
Tags: @product
1:33.418
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 57.985
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 25.716
And I take note of which tps features are available 4.790
Then a Tails persistence partition exists on USB drive "old" 0.561
And I shutdown Tails and wait for the computer to power off 4.065
After features/support/hooks.rb:339 0.467
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.182
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.816
Then Tails is running from USB drive "old" 0.339
And all tps features are active 5.677
When I write some files expected to persist 1.527
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.314
And all persistent directories from the old Tails version have safe access rights 2.104
And I take note of which tps features are available 3.973
And I shutdown Tails and wait for the computer to power off 4.121
# 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.069
After features/support/hooks.rb:339 0.176
After features/support/hooks.rb:108 0.007
Tags: @product
2:15.632
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.035
And I log in to a new session 15.064
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.922
And I plug USB drive "to_upgrade" 2.297
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.175
Then the running Tails is installed on USB drive "to_upgrade" 16.813
And I unplug USB drive "to_upgrade" 0.161
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:339 2.589
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.228
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.102
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.030
Then all tps features from the old Tails version are active 1.061
And Tails is running from USB drive "to_upgrade" 0.266
And the boot device has safe access rights 3.301
And the expected persistent files created with the old Tails version are present in the filesystem 1.335
And all persistent directories from the old Tails version have safe access rights 2.129
After features/support/hooks.rb:339 0.705
After features/support/hooks.rb:108 0.038
Tags: @product @automatic_upgrade
4:1.689
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.375
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.181
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.018
And Tor is ready 13.338
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.897
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.205
Given I shutdown Tails and wait for the computer to power off 6.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.916
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 5.514
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.210
# 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.258
When the network is plugged 0.026
And Tor is ready 11.328
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.592
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.404
Given I shutdown Tails and wait for the computer to power off 4.514
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.335
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 6.181
And the file system changes introduced in version 6.3~testoverlayfs are present 0.409
And only the 6.3~testoverlayfs SquashFS delta is installed 0.092
# 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.180
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.032
And Tor is ready 10.154
Then the Upgrader considers the system as up-to-date 10.608
# 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 5.079
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.430
After features/support/hooks.rb:339 0.744
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
20.981
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 7.786
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 9.362
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.440
After features/support/hooks.rb:339 0.779
After features/support/hooks.rb:108 0.000