Project Number Date
test_Tails_ISO_stable 6203 15 Mar 2026, 06:47

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:22.099 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:11.970
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.049
When I start Tails from USB drive "old" with network unplugged 54.651
Then the boot device has safe access rights 2.558
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:331 3.604
After features/support/hooks.rb:100 0.016
Tags: @product
1:26.289
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.043
And I start Tails from USB drive "old" with network unplugged and I login 52.664
Then Tails is running from USB drive "old" 0.266
And I create a persistent partition 24.132
And I take note of which tps features are available 0.715
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 7.962
After features/support/hooks.rb:331 0.554
After features/support/hooks.rb:100 0.006
Tags: @product
1:19.562
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.419
Then Tails is running from USB drive "old" 0.241
And all tps features are active 1.049
When I write some files expected to persist 1.319
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 1.889
And I take note of which tps features are available 0.147
And I shutdown Tails and wait for the computer to power off 4.097
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.686
After features/support/hooks.rb:331 0.269
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.945
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.559
And I log in to a new session 10.076
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.905
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.523
Then the running Tails is installed on USB drive "to_upgrade" 15.380
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 2.514
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.355
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.647
Then all tps features from the old Tails version are active 0.954
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.270
And the expected persistent files created with the old Tails version are present in the filesystem 1.170
And all persistent directories from the old Tails version have safe access rights 1.985
After features/support/hooks.rb:331 0.912
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:43.303
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.355
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.186
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.016
And Tor is ready 19.565
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.102
Given I shutdown Tails and wait for the computer to power off 14.631
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.347
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.127
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.114
# 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.201
When the network is plugged 0.014
And Tor is ready 40.152
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.998
Given I shutdown Tails and wait for the computer to power off 18.600
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.026
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.044
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.015
And Tor is ready 21.414
Then the Upgrader considers the system as up-to-date 0.095
# 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.334
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.422
After features/support/hooks.rb:331 0.625
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
24.672
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.441
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
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.014
And Tor is ready 16.547
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.346
After features/support/hooks.rb:331 1.224
After features/support/hooks.rb:100 0.000