Project Number Date
test_Tails_ISO_21651-persist-gnome-software-based-on-17367 4 08 Aug 2026, 09:14

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:18.336 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:16.398
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 12.921
When I start Tails from USB drive "old" with network unplugged 59.630
Then the boot device has safe access rights 2.116
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:339 3.659
After features/support/hooks.rb:108 0.026
Tags: @product
1:19.564
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login 47.506
Then Tails is running from USB drive "old" 0.196
And I create a persistent partition 22.519
And I take note of which tps features are available 6.191
Then a Tails persistence partition exists on USB drive "old" 0.479
And I shutdown Tails and wait for the computer to power off 2.567
After features/support/hooks.rb:339 0.315
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.219
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.296
Then Tails is running from USB drive "old" 0.211
And all tps features are active 7.555
When I write some files expected to persist 1.052
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.136
And all persistence configuration files have safe access rights 0.257
And all persistent directories from the old Tails version have safe access rights 1.684
And I take note of which tps features are available 6.355
And I shutdown Tails and wait for the computer to power off 2.585
# 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.986
After features/support/hooks.rb:339 0.068
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.129
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 without a persistent partition and stopped at Tails Greeter's login screen 8.282
And I log in to a new session 10.799
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.652
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.236
Then the running Tails is installed on USB drive "to_upgrade" 17.687
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.114
After features/support/hooks.rb:339 1.915
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.934
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.434
Then all tps features from the old Tails version are active 1.075
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 1.831
And the expected persistent files created with the old Tails version are present in the filesystem 0.856
And all persistent directories from the old Tails version have safe access rights 1.419
After features/support/hooks.rb:339 0.710
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:36.870
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.915
And no SquashFS delta is installed 0.064
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.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.178
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.234
When the network is plugged 0.037
And Tor is ready 11.536
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.094
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.424
Given I shutdown Tails and wait for the computer to power off 5.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.614
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 10.076
And the file system changes introduced in version 6.2~testoverlayfs are present 0.189
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.149
When the network is plugged 0.036
And Tor is ready 9.994
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.483
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.477
Given I shutdown Tails and wait for the computer to power off 4.175
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.442
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 10.208
And the file system changes introduced in version 6.3~testoverlayfs are present 0.262
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.152
When the network is plugged 0.032
And Tor is ready 10.676
Then the Upgrader considers the system as up-to-date 0.100
# 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.102
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.316
After features/support/hooks.rb:339 0.953
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.218
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.689
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.026
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 8.232
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.893
After features/support/hooks.rb:339 0.913
After features/support/hooks.rb:108 0.000