Project Number Date
test_Tails_ISO_devel 4206 03 Feb 2026, 12:51

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 18:16.342 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:46.044
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 33.841
When I start Tails from USB drive "old" with network unplugged 1:7.176
Then the boot device has safe access rights 2.946
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:331 1.596
After features/support/hooks.rb:100 0.009
Tags: @product
1:42.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 1:3.478
Then Tails is running from USB drive "old" 0.524
And I create a persistent partition 28.806
And I take note of which tps features are available 1.242
Then a Tails persistence partition exists on USB drive "old" 0.647
And I shutdown Tails and wait for the computer to power off 7.876
After features/support/hooks.rb:331 0.240
After features/support/hooks.rb:100 0.012
Tags: @product
1:47.393
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:15.890
Then Tails is running from USB drive "old" 0.308
And all tps features are active 1.872
When I write some files expected to persist 1.486
# 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.375
And all persistent directories from the old Tails version have safe access rights 2.429
And I take note of which tps features are available 0.513
And I shutdown Tails and wait for the computer to power off 4.874
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.256
After features/support/hooks.rb:331 0.489
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.840
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.188
And I log in to a new session 13.899
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.777
And I plug USB drive "to_upgrade" 2.698
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.641
Then the running Tails is installed on USB drive "to_upgrade" 21.957
And I unplug USB drive "to_upgrade" 0.393
And I unplug USB drive "__internal" 0.283
After features/support/hooks.rb:331 2.655
After features/support/hooks.rb:100 0.000
Tags: @product
1:53.516
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.172
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:33.873
Then all tps features from the old Tails version are active 11.684
And Tails is running from USB drive "to_upgrade" 0.318
And the boot device has safe access rights 3.592
And the expected persistent files created with the old Tails version are present in the filesystem 1.601
And all persistent directories from the old Tails version have safe access rights 2.273
After features/support/hooks.rb:331 1.689
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:48.949
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 1:13.589
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.403
When the network is plugged 6.882
And Tor is ready 34.838
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.261
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 40.740
Given I shutdown Tails and wait for the computer to power off 11.086
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.791
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 4.661
And the file system changes introduced in version 6.2~testoverlayfs are present 0.385
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.176
# 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.267
When the network is plugged 0.115
And Tor is ready 17.511
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 12.809
Given I shutdown Tails and wait for the computer to power off 9.964
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:33.806
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 10.028
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.054
And Tor is ready 15.710
Then the Upgrader considers the system as up-to-date 0.130
# 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 6.369
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.770
After features/support/hooks.rb:331 2.111
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
36.855
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 18.999
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 1.431
And Tor is ready 12.630
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.381
After features/support/hooks.rb:331 9.853
After features/support/hooks.rb:100 0.000