Project Number Date
test_Tails_ISO_tps-restart-gnome-software 8 14 Jun 2026, 18:23

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:52.441 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:14.232
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.106
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 12.829
When I start Tails from USB drive "old" with network unplugged 56.840
Then the boot device has safe access rights 2.691
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 3.863
After features/support/hooks.rb:108 0.048
Tags: @product
1:26.862
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login 50.769
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 24.209
And I take note of which tps features are available 4.231
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 6.769
After features/support/hooks.rb:339 0.597
After features/support/hooks.rb:108 0.015
Tags: @product
1:35.815
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.127
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.199
Then Tails is running from USB drive "old" 0.244
And all tps features are active 4.977
When I write some files expected to persist 1.204
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.327
And all persistent directories from the old Tails version have safe access rights 1.913
And I take note of which tps features are available 3.591
And I shutdown Tails and wait for the computer to power off 8.260
# 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" 11.805
After features/support/hooks.rb:339 0.539
After features/support/hooks.rb:108 0.017
Tags: @product
2:8.546
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.693
And I log in to a new session 11.755
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.691
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.180
Then the running Tails is installed on USB drive "to_upgrade" 14.579
And I unplug USB drive "to_upgrade" 0.286
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 1.976
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.908
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.258
Then all tps features from the old Tails version are active 1.078
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.330
And the expected persistent files created with the old Tails version are present in the filesystem 1.066
And all persistent directories from the old Tails version have safe access rights 1.737
After features/support/hooks.rb:339 0.796
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:54.265
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.334
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
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.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.015
And Tor is ready 13.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.712
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.070
Given I shutdown Tails and wait for the computer to power off 9.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.367
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.231
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.230
When the network is plugged 0.016
And Tor is ready 10.892
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.028
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.808
Given I shutdown Tails and wait for the computer to power off 6.823
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.767
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.464
And the file system changes introduced in version 6.3~testoverlayfs are present 0.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.016
And Tor is ready 10.135
Then the Upgrader considers the system as up-to-date 10.578
# 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.369
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.431
After features/support/hooks.rb:339 0.752
After features/support/hooks.rb:108 0.039
Tags: @product @automatic_upgrade
20.810
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.903
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
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.054
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.665
After features/support/hooks.rb:339 0.944
After features/support/hooks.rb:108 0.000