Project Number Date
test_Tails_ISO_21651-persist-gnome-software-dconf-state 6 25 Jul 2026, 03:48

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:8.710 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:24.586
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.680
When I start Tails from USB drive "old" with network unplugged 1:5.895
Then the boot device has safe access rights 3.221
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:339 1.566
After features/support/hooks.rb:108 0.029
Tags: @product
1:27.970
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 53.440
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 25.013
And I take note of which tps features are available 4.450
Then a Tails persistence partition exists on USB drive "old" 0.582
And I shutdown Tails and wait for the computer to power off 4.171
After features/support/hooks.rb:339 0.413
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.053
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.883
Then Tails is running from USB drive "old" 0.265
And all tps features are active 5.354
When I write some files expected to persist 1.413
# 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.313
And all persistent directories from the old Tails version have safe access rights 1.979
And I take note of which tps features are available 3.854
And I shutdown Tails and wait for the computer to power off 3.988
# 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.738
After features/support/hooks.rb:339 0.307
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.443
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.064
And I log in to a new session 12.044
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.963
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.350
Then the running Tails is installed on USB drive "to_upgrade" 15.537
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 2.520
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.034
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.421
Then all tps features from the old Tails version are active 1.065
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.433
And the expected persistent files created with the old Tails version are present in the filesystem 1.050
And all persistent directories from the old Tails version have safe access rights 1.794
After features/support/hooks.rb:339 0.744
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:53.917
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 with a persistent partition enabled and logged in 8.045
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.343
When the network is plugged 0.014
And Tor is ready 13.291
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.300
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.797
Given I shutdown Tails and wait for the computer to power off 5.638
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.458
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.601
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.207
When the network is plugged 0.018
And Tor is ready 10.555
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.687
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.637
Given I shutdown Tails and wait for the computer to power off 4.051
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.103
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.624
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.209
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.013
And Tor is ready 10.276
Then the Upgrader considers the system as up-to-date 10.606
# 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.272
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.356
After features/support/hooks.rb:339 1.050
After features/support/hooks.rb:108 0.068
Tags: @product @automatic_upgrade
21.703
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.498
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.097
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.820
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.948
After features/support/hooks.rb:339 1.058
After features/support/hooks.rb:108 0.000