Project Number Date
test_Tails_ISO_21691-gitlab-triage-use-trusted-image 1 23 Jul 2026, 16: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 12:48.603 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:25.498
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.666
When I start Tails from USB drive "old" with network unplugged 1:5.527
Then the boot device has safe access rights 3.306
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.088
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 1.756
After features/support/hooks.rb:108 0.007
Tags: @product
1:33.333
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 57.850
Then Tails is running from USB drive "old" 0.222
And I create a persistent partition 25.360
And I take note of which tps features are available 4.922
Then a Tails persistence partition exists on USB drive "old" 0.645
And I shutdown Tails and wait for the computer to power off 4.274
After features/support/hooks.rb:339 0.530
After features/support/hooks.rb:108 0.008
Tags: @product
1:40.311
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.101
Then Tails is running from USB drive "old" 0.300
And all tps features are active 5.266
When I write some files expected to persist 1.458
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 2.085
And I take note of which tps features are available 4.467
And I shutdown Tails and wait for the computer to power off 4.274
# 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.788
After features/support/hooks.rb:339 0.590
After features/support/hooks.rb:108 0.008
Tags: @product
2:15.520
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 without a persistent partition and stopped at Tails Greeter's login screen 8.998
And I log in to a new session 13.663
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.096
And I plug USB drive "to_upgrade" 2.291
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.393
Then the running Tails is installed on USB drive "to_upgrade" 16.797
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 2.665
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.096
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.065
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.619
Then all tps features from the old Tails version are active 1.143
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 2.619
And the expected persistent files created with the old Tails version are present in the filesystem 1.262
And all persistent directories from the old Tails version have safe access rights 2.097
After features/support/hooks.rb:339 0.772
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
4:13.687
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.871
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.020
And Tor is ready 14.496
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.505
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.263
Given I shutdown Tails and wait for the computer to power off 6.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.398
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.547
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.250
When the network is plugged 0.059
And Tor is ready 10.216
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.913
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.219
Given I shutdown Tails and wait for the computer to power off 4.178
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.398
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.350
And the file system changes introduced in version 6.3~testoverlayfs are present 0.407
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.020
And Tor is ready 20.604
Then the Upgrader considers the system as up-to-date 10.655
# 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.753
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.437
After features/support/hooks.rb:339 0.788
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.155
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.291
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
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.038
And Tor is ready 10.652
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.811
After features/support/hooks.rb:339 0.589
After features/support/hooks.rb:108 0.000