Project Number Date
test_Tails_ISO_release-process-7.7.3 4 11 May 2026, 18:27

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 13:22.155 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:14.180
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.015
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.367
When I start Tails from USB drive "old" with network unplugged 55.844
Then the boot device has safe access rights 3.049
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:331 3.685
After features/support/hooks.rb:100 0.011
Tags: @product
1:32.596
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login 56.935
Then Tails is running from USB drive "old" 0.269
And I create a persistent partition 25.345
And I take note of which tps features are available 0.781
Then a Tails persistence partition exists on USB drive "old" 0.681
And I shutdown Tails and wait for the computer to power off 8.483
After features/support/hooks.rb:331 0.312
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.252
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.363
Then Tails is running from USB drive "old" 0.270
And all tps features are active 1.192
When I write some files expected to persist 1.526
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.513
And all persistent directories from the old Tails version have safe access rights 2.094
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 8.175
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.677
After features/support/hooks.rb:331 0.598
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.383
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.191
And I log in to a new session 13.098
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.922
And I plug USB drive "to_upgrade" 2.261
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.696
Then the running Tails is installed on USB drive "to_upgrade" 17.822
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:331 2.418
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.559
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.122
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.625
Then all tps features from the old Tails version are active 1.022
And Tails is running from USB drive "to_upgrade" 0.277
And the boot device has safe access rights 2.939
And the expected persistent files created with the old Tails version are present in the filesystem 1.467
And all persistent directories from the old Tails version have safe access rights 2.103
After features/support/hooks.rb:331 0.886
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:5.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.032
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.022
And Tor is ready 22.810
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.387
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.715
Given I shutdown Tails and wait for the computer to power off 20.619
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.817
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.244
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.253
When the network is plugged 0.017
And Tor is ready 27.137
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.367
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.461
Given I shutdown Tails and wait for the computer to power off 17.883
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.766
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.105
And the file system changes introduced in version 6.3~testoverlayfs are present 0.358
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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.013
And Tor is ready 26.200
Then the Upgrader considers the system as up-to-date 0.161
# 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 5.562
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.455
After features/support/hooks.rb:331 1.312
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
26.792
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.785
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 18.270
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
After features/support/hooks.rb:331 0.999
After features/support/hooks.rb:100 0.000