Project Number Date
test_Tails_ISO_stable 6405 26 May 2026, 20:04

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 12:13.245 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:10.059
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.842
When I start Tails from USB drive "old" with network unplugged 51.404
Then the boot device has safe access rights 2.942
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:335 1.451
After features/support/hooks.rb:104 0.008
Tags: @product
1:32.366
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 57.445
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 26.418
And I take note of which tps features are available 0.382
Then a Tails persistence partition exists on USB drive "old" 0.652
And I shutdown Tails and wait for the computer to power off 7.121
After features/support/hooks.rb:335 0.513
After features/support/hooks.rb:104 0.008
Tags: @product
1:33.678
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.832
Then Tails is running from USB drive "old" 0.332
And all tps features are active 1.595
When I write some files expected to persist 1.621
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.421
And all persistent directories from the old Tails version have safe access rights 2.295
And I take note of which tps features are available 0.205
And I shutdown Tails and wait for the computer to power off 4.226
# 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" 13.864
After features/support/hooks.rb:335 0.170
After features/support/hooks.rb:104 0.008
Tags: @product
2:17.228
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.776
And I log in to a new session 14.473
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.015
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.107
Then the running Tails is installed on USB drive "to_upgrade" 16.279
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.159
After features/support/hooks.rb:335 0.995
After features/support/hooks.rb:104 0.000
Tags: @product
1:16.984
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.364
Then all tps features from the old Tails version are active 1.030
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.661
And the expected persistent files created with the old Tails version are present in the filesystem 1.287
And all persistent directories from the old Tails version have safe access rights 2.312
After features/support/hooks.rb:335 0.814
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
4:0.620
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.491
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.259
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.017
And Tor is ready 13.088
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.109
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.083
Given I shutdown Tails and wait for the computer to power off 11.059
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.565
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 1.417
And the file system changes introduced in version 6.2~testoverlayfs are present 0.322
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.153
# 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.205
When the network is plugged 0.034
And Tor is ready 12.161
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.877
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.663
Given I shutdown Tails and wait for the computer to power off 7.256
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.147
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.289
And the file system changes introduced in version 6.3~testoverlayfs are present 0.407
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.016
And Tor is ready 10.592
Then the Upgrader considers the system as up-to-date 10.563
# 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.876
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.681
After features/support/hooks.rb:335 0.925
After features/support/hooks.rb:104 0.036
Tags: @product @automatic_upgrade
22.307
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 with a persistent partition enabled and logged in 8.293
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 11.423
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.179
After features/support/hooks.rb:335 1.070
After features/support/hooks.rb:104 0.000