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

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:19.687 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:15.594
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.118
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" 12.928
When I start Tails from USB drive "old" with network unplugged 59.091
Then the boot device has safe access rights 1.838
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.152
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.679
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.973
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 46.802
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 22.057
And I take note of which tps features are available 6.051
Then a Tails persistence partition exists on USB drive "old" 0.466
And I shutdown Tails and wait for the computer to power off 5.301
After features/support/hooks.rb:339 0.324
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.257
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.538
Then Tails is running from USB drive "old" 0.186
And all tps features are active 7.012
When I write some files expected to persist 1.034
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.120
And all persistence configuration files have safe access rights 0.259
And all persistent directories from the old Tails version have safe access rights 1.667
And I take note of which tps features are available 5.674
And I shutdown Tails and wait for the computer to power off 2.499
# 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.185
After features/support/hooks.rb:339 0.563
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.999
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.222
And I log in to a new session 12.880
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.549
And I plug USB drive "to_upgrade" 2.309
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.265
Then the running Tails is installed on USB drive "to_upgrade" 17.527
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 1.761
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.478
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.665
Then all tps features from the old Tails version are active 1.003
And Tails is running from USB drive "to_upgrade" 0.185
And the boot device has safe access rights 2.085
And the expected persistent files created with the old Tails version are present in the filesystem 0.868
And all persistent directories from the old Tails version have safe access rights 1.599
After features/support/hooks.rb:339 0.617
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
3:29.269
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.002
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.174
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.169
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.312
When the network is plugged 0.038
And Tor is ready 11.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.981
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.089
Given I shutdown Tails and wait for the computer to power off 5.188
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.965
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.910
And the file system changes introduced in version 6.2~testoverlayfs are present 0.156
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.097
# 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.139
When the network is plugged 0.034
And Tor is ready 10.232
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.882
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.572
Given I shutdown Tails and wait for the computer to power off 2.615
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.814
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 9.740
And the file system changes introduced in version 6.3~testoverlayfs are present 0.273
And only the 6.3~testoverlayfs SquashFS delta is installed 0.030
# 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.091
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.033
And Tor is ready 9.932
Then the Upgrader considers the system as up-to-date 0.077
# 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.074
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.305
After features/support/hooks.rb:339 1.016
After features/support/hooks.rb:108 0.054
Tags: @product @automatic_upgrade
27.115
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 7.795
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
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.050
And Tor is ready 17.076
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.919
After features/support/hooks.rb:339 0.537
After features/support/hooks.rb:108 0.000