Project Number Date
test_Tails_ISO_devel 4395 14 May 2026, 11:10

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:13.231 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:5.163
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.618
When I start Tails from USB drive "old" with network unplugged 46.660
Then the boot device has safe access rights 2.986
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.248
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:335 1.347
After features/support/hooks.rb:104 0.007
Tags: @product
1:30.422
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 55.582
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 25.067
And I take note of which tps features are available 0.378
Then a Tails persistence partition exists on USB drive "old" 0.599
And I shutdown Tails and wait for the computer to power off 8.413
After features/support/hooks.rb:335 0.465
After features/support/hooks.rb:104 0.009
Tags: @product
1:23.878
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.778
Then Tails is running from USB drive "old" 0.280
And all tps features are active 1.270
When I write some files expected to persist 1.327
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 1.997
And I take note of which tps features are available 0.175
And I shutdown Tails and wait for the computer to power off 4.435
# 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.005
After features/support/hooks.rb:335 0.504
After features/support/hooks.rb:104 0.010
Tags: @product
2:8.771
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.559
And I log in to a new session 11.845
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.707
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.019
Then the running Tails is installed on USB drive "to_upgrade" 15.185
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:335 2.077
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.528
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.946
Then all tps features from the old Tails version are active 0.933
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 2.445
And the expected persistent files created with the old Tails version are present in the filesystem 1.057
And all persistent directories from the old Tails version have safe access rights 1.855
After features/support/hooks.rb:335 0.705
After features/support/hooks.rb:104 0.006
3:39.121
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.047
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.433
When the network is plugged 0.021
And Tor is ready 13.203
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.358
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.791
Given I shutdown Tails and wait for the computer to power off 6.858
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.015
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.084
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.220
When the network is plugged 0.014
And Tor is ready 10.313
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.853
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.931
Given I shutdown Tails and wait for the computer to power off 8.006
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.022
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.368
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.017
And Tor is ready 9.979
Then the Upgrader considers the system as up-to-date 10.552
# 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.071
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:335 0.786
After features/support/hooks.rb:104 0.011
20.344
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.281
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.949
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.760
After features/support/hooks.rb:335 0.881
After features/support/hooks.rb:104 0.000