Project Number Date
test_Tails_ISO_make-cloner-findable-via-backup-keyword 5 25 Oct 2026, 02:42

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.146 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.089
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.450
When I start Tails from USB drive "old" with network unplugged 57.503
Then the boot device has safe access rights 2.448
And Tails is running from USB drive "old" 0.177
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.152
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 1.063
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.389
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 48.784
Then Tails is running from USB drive "old" 0.199
And I create a persistent partition 24.174
And I take note of which tps features are available 6.535
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 4.088
After features/support/hooks.rb:339 0.513
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.039
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 with persistence enabled 1:1.214
Then Tails is running from USB drive "old" 0.225
And all tps features are active 7.007
When I write some files expected to persist 0.991
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.213
And all persistent directories from the old Tails version have safe access rights 2.023
And I take note of which tps features are available 5.995
And I shutdown Tails and wait for the computer to power off 2.683
# 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.422
After features/support/hooks.rb:339 0.224
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.001
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.754
And I log in to a new session 11.511
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.670
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.241
Then the running Tails is installed on USB drive "to_upgrade" 18.337
And I unplug USB drive "to_upgrade" 0.145
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 1.967
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.555
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.203
Then all tps features from the old Tails version are active 1.011
And Tails is running from USB drive "to_upgrade" 0.191
And the boot device has safe access rights 2.595
And the expected persistent files created with the old Tails version are present in the filesystem 0.863
And all persistent directories from the old Tails version have safe access rights 1.609
After features/support/hooks.rb:339 0.702
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
3:27.874
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.185
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.304
When the network is plugged 0.027
And Tor is ready 12.569
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.014
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.428
Given I shutdown Tails and wait for the computer to power off 5.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.524
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.150
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.198
When the network is plugged 0.025
And Tor is ready 10.425
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.325
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.705
Given I shutdown Tails and wait for the computer to power off 5.090
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.910
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.399
And the file system changes introduced in version 6.3~testoverlayfs are present 0.244
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.165
When the network is plugged 0.045
And Tor is ready 10.156
Then the Upgrader considers the system as up-to-date 0.095
# 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 2.970
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.318
After features/support/hooks.rb:339 0.941
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.197
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.765
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.555
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.429
After features/support/hooks.rb:339 0.952
After features/support/hooks.rb:108 0.000