Project Number Date
test_Tails_ISO_make-cloner-findable-via-backup-keyword 2 22 Oct 2026, 02:46

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.194 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.499
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.210
When I start Tails from USB drive "old" with network unplugged 54.701
Then the boot device has safe access rights 2.718
And Tails is running from USB drive "old" 0.281
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:339 3.755
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.587
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 48.724
Then Tails is running from USB drive "old" 0.174
And I create a persistent partition 24.081
And I take note of which tps features are available 7.911
Then a Tails persistence partition exists on USB drive "old" 0.566
And I shutdown Tails and wait for the computer to power off 4.031
After features/support/hooks.rb:339 0.239
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.876
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 with persistence enabled 1:1.591
Then Tails is running from USB drive "old" 0.211
And all tps features are active 8.429
When I write some files expected to persist 1.097
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.268
And all persistent directories from the old Tails version have safe access rights 1.641
And I take note of which tps features are available 7.259
And I shutdown Tails and wait for the computer to power off 2.498
# 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.613
After features/support/hooks.rb:339 0.391
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.040
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.225
And I log in to a new session 11.459
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.736
And I plug USB drive "to_upgrade" 2.324
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.155
Then the running Tails is installed on USB drive "to_upgrade" 17.892
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.811
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.415
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.263
Then all tps features from the old Tails version are active 1.165
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.019
And the expected persistent files created with the old Tails version are present in the filesystem 0.947
And all persistent directories from the old Tails version have safe access rights 1.720
After features/support/hooks.rb:339 0.741
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
3:25.885
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.018
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.215
When the network is plugged 0.041
And Tor is ready 12.211
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.301
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.308
Given I shutdown Tails and wait for the computer to power off 5.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.339
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.774
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
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.102
# 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.178
When the network is plugged 0.024
And Tor is ready 10.415
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.304
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.651
Given I shutdown Tails and wait for the computer to power off 3.957
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.374
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.145
And the file system changes introduced in version 6.3~testoverlayfs are present 0.261
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.163
When the network is plugged 0.038
And Tor is ready 10.135
Then the Upgrader considers the system as up-to-date 0.082
# 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.144
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.340
After features/support/hooks.rb:339 1.036
After features/support/hooks.rb:108 0.025
Tags: @product @automatic_upgrade
17.889
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.971
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.029
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 8.004
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.538
After features/support/hooks.rb:339 0.800
After features/support/hooks.rb:108 0.000