Project Number Date
test_Tails_ISO_devel 4447 15 Jun 2026, 11:17

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:24.340 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:1.130
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.121
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 12.990
When I start Tails from USB drive "old" with network unplugged 43.760
Then the boot device has safe access rights 2.532
And Tails is running from USB drive "old" 0.200
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 3.436
After features/support/hooks.rb:108 0.017
Tags: @product
1:23.558
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.116
And I start Tails from USB drive "old" with network unplugged and I login 52.195
Then Tails is running from USB drive "old" 0.240
And I create a persistent partition 23.987
And I take note of which tps features are available 3.793
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 2.726
After features/support/hooks.rb:339 0.385
After features/support/hooks.rb:108 0.017
Tags: @product
1:32.664
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.127
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.020
Then Tails is running from USB drive "old" 0.214
And all tps features are active 5.002
When I write some files expected to persist 1.231
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.139
And all persistence configuration files have safe access rights 0.340
And all persistent directories from the old Tails version have safe access rights 1.826
And I take note of which tps features are available 3.814
And I shutdown Tails and wait for the computer to power off 6.806
# 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" 12.141
After features/support/hooks.rb:339 0.171
After features/support/hooks.rb:108 0.017
Tags: @product
2:9.667
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.072
And I log in to a new session 12.134
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.760
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.278
Then the running Tails is installed on USB drive "to_upgrade" 14.947
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 0.637
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.855
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.114
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.178
Then all tps features from the old Tails version are active 1.045
And Tails is running from USB drive "to_upgrade" 0.232
And the boot device has safe access rights 2.320
And the expected persistent files created with the old Tails version are present in the filesystem 1.187
And all persistent directories from the old Tails version have safe access rights 1.777
After features/support/hooks.rb:339 0.858
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:48.194
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.362
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.290
When the network is plugged 0.013
And Tor is ready 13.134
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.818
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.884
Given I shutdown Tails and wait for the computer to power off 7.139
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.377
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.568
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.168
# 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.244
When the network is plugged 0.020
And Tor is ready 9.943
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.569
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.529
Given I shutdown Tails and wait for the computer to power off 8.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.213
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.704
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.016
And Tor is ready 10.005
Then the Upgrader considers the system as up-to-date 10.540
# 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 4.319
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:339 0.688
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
19.269
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.775
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.166
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 8.463
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.620
After features/support/hooks.rb:339 0.948
After features/support/hooks.rb:108 0.000