Project Number Date
test_Tails_ISO_21651-persist-gnome-software-based-on-17367 6 10 Aug 2026, 09:09

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:32.312 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:13.289
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.500
When I start Tails from USB drive "old" with network unplugged 56.148
Then the boot device has safe access rights 1.872
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 1.562
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.894
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 48.518
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 22.412
And I take note of which tps features are available 6.234
Then a Tails persistence partition exists on USB drive "old" 0.451
And I shutdown Tails and wait for the computer to power off 3.952
After features/support/hooks.rb:339 0.435
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.911
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.643
Then Tails is running from USB drive "old" 0.209
And all tps features are active 7.899
When I write some files expected to persist 1.210
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 1.702
And I take note of which tps features are available 6.069
And I shutdown Tails and wait for the computer to power off 4.083
# 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.507
After features/support/hooks.rb:339 0.434
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.323
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.146
And I log in to a new session 11.986
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.669
And I plug USB drive "to_upgrade" 2.199
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.118
Then the running Tails is installed on USB drive "to_upgrade" 17.815
And I unplug USB drive "to_upgrade" 0.255
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.061
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.100
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.061
Then all tps features from the old Tails version are active 0.991
And Tails is running from USB drive "to_upgrade" 0.196
And the boot device has safe access rights 2.154
And the expected persistent files created with the old Tails version are present in the filesystem 0.928
And all persistent directories from the old Tails version have safe access rights 1.685
After features/support/hooks.rb:339 0.670
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:40.514
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.722
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.326
When the network is plugged 0.027
And Tor is ready 12.102
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.304
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.626
Given I shutdown Tails and wait for the computer to power off 5.438
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.123
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 11.303
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.092
# 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.168
When the network is plugged 0.036
And Tor is ready 10.503
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.087
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.638
Given I shutdown Tails and wait for the computer to power off 2.705
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.559
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.394
And the file system changes introduced in version 6.3~testoverlayfs are present 0.271
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.092
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.024
And Tor is ready 10.238
Then the Upgrader considers the system as up-to-date 0.086
# 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 3.165
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.376
After features/support/hooks.rb:339 0.894
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.278
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 8.613
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.837
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.496
After features/support/hooks.rb:339 0.856
After features/support/hooks.rb:108 0.000