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

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:54.721 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:18.909
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.116
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.635
When I start Tails from USB drive "old" with network unplugged 1:1.341
Then the boot device has safe access rights 2.167
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.105
After features/support/hooks.rb:339 3.709
After features/support/hooks.rb:108 0.006
Tags: @product
1:21.814
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login 49.136
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 22.743
And I take note of which tps features are available 6.369
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 2.695
After features/support/hooks.rb:339 0.547
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.543
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.574
Then Tails is running from USB drive "old" 0.225
And all tps features are active 7.421
When I write some files expected to persist 1.023
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.235
And all persistent directories from the old Tails version have safe access rights 1.502
And I take note of which tps features are available 6.512
And I shutdown Tails and wait for the computer to power off 2.576
# 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.234
After features/support/hooks.rb:339 0.264
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.501
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.343
And I log in to a new session 11.945
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.572
And I plug USB drive "to_upgrade" 2.183
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.828
Then the running Tails is installed on USB drive "to_upgrade" 18.281
And I unplug USB drive "to_upgrade" 0.183
And I unplug USB drive "__internal" 0.162
After features/support/hooks.rb:339 1.695
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.743
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.116
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.776
Then all tps features from the old Tails version are active 1.042
And Tails is running from USB drive "to_upgrade" 0.191
And the boot device has safe access rights 2.066
And the expected persistent files created with the old Tails version are present in the filesystem 0.881
And all persistent directories from the old Tails version have safe access rights 1.667
After features/support/hooks.rb:339 0.894
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:54.032
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.268
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.323
When the network is plugged 0.037
And Tor is ready 17.979
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.190
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.169
Given I shutdown Tails and wait for the computer to power off 5.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.832
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 10.234
And the file system changes introduced in version 6.2~testoverlayfs are present 0.200
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.188
When the network is plugged 0.024
And Tor is ready 10.546
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.470
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.520
Given I shutdown Tails and wait for the computer to power off 2.528
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.069
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 10.610
And the file system changes introduced in version 6.3~testoverlayfs are present 0.385
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.035
And Tor is ready 10.061
Then the Upgrader considers the system as up-to-date 10.425
# 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.114
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.350
After features/support/hooks.rb:339 0.771
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
26.176
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.808
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.040
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 16.521
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.505
After features/support/hooks.rb:339 1.134
After features/support/hooks.rb:108 0.000