Project Number Date
test_Tails_ISO_stable 6177 27 Feb 2026, 11:57

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 15:21.308 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:38.369
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 31.499
When I start Tails from USB drive "old" with network unplugged 1:1.518
Then the boot device has safe access rights 3.069
And Tails is running from USB drive "old" 0.364
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.332
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:331 4.026
After features/support/hooks.rb:100 0.009
Tags: @product
1:41.309
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:2.528
Then Tails is running from USB drive "old" 0.637
And I create a persistent partition 28.381
And I take note of which tps features are available 1.131
Then a Tails persistence partition exists on USB drive "old" 0.656
And I shutdown Tails and wait for the computer to power off 7.810
After features/support/hooks.rb:331 0.626
After features/support/hooks.rb:100 0.008
Tags: @product
1:45.040
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:12.126
Then Tails is running from USB drive "old" 0.282
And all tps features are active 2.003
When I write some files expected to persist 1.583
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.540
And all persistent directories from the old Tails version have safe access rights 2.185
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 7.463
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.004
After features/support/hooks.rb:331 0.361
After features/support/hooks.rb:100 0.011
Tags: @product
2:43.847
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.034
And I log in to a new session 13.929
And I clone USB drive "old" to a new USB drive "to_upgrade" 7.168
And I plug USB drive "to_upgrade" 2.598
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.984
Then the running Tails is installed on USB drive "to_upgrade" 20.708
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:331 2.479
After features/support/hooks.rb:100 0.000
Tags: @product
1:23.383
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.255
Then all tps features from the old Tails version are active 1.312
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.863
And the expected persistent files created with the old Tails version are present in the filesystem 1.185
And all persistent directories from the old Tails version have safe access rights 2.276
After features/support/hooks.rb:331 1.023
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:37.905
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.723
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
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.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.521
When the network is plugged 0.056
And Tor is ready 24.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.619
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.054
Given I shutdown Tails and wait for the computer to power off 17.035
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.043
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.253
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.275
When the network is plugged 0.049
And Tor is ready 41.989
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.711
Given I shutdown Tails and wait for the computer to power off 18.197
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.902
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.236
And the file system changes introduced in version 6.3~testoverlayfs are present 0.424
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.058
And Tor is ready 22.324
Then the Upgrader considers the system as up-to-date 0.123
# 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.273
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.525
After features/support/hooks.rb:331 1.221
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
31.452
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.477
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 19.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.585
After features/support/hooks.rb:331 1.064
After features/support/hooks.rb:100 0.000