Project Number Date
test_Tails_ISO_stable 6118 04 Feb 2026, 11: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 11:43.775 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:9.738
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.429
When I start Tails from USB drive "old" with network unplugged 51.832
Then the boot device has safe access rights 2.715
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:331 4.013
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.585
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 52.583
Then Tails is running from USB drive "old" 0.199
And I create a persistent partition 23.626
And I take note of which tps features are available 0.666
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 7.918
After features/support/hooks.rb:331 0.290
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.394
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.573
Then Tails is running from USB drive "old" 0.222
And all tps features are active 0.998
When I write some files expected to persist 1.385
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.161
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.840
And I take note of which tps features are available 0.152
And I shutdown Tails and wait for the computer to power off 7.922
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.824
After features/support/hooks.rb:331 0.431
After features/support/hooks.rb:100 0.006
Tags: @product
2:10.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.616
And I log in to a new session 10.696
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.799
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.669
Then the running Tails is installed on USB drive "to_upgrade" 15.352
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 3.683
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.272
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.209
Then all tps features from the old Tails version are active 0.893
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 2.631
And the expected persistent files created with the old Tails version are present in the filesystem 1.146
And all persistent directories from the old Tails version have safe access rights 2.017
After features/support/hooks.rb:331 0.997
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:37.155
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.960
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.014
And Tor is ready 13.312
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.372
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.232
Given I shutdown Tails and wait for the computer to power off 9.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.997
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.169
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
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.157
# 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.015
And Tor is ready 11.278
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.829
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.268
Given I shutdown Tails and wait for the computer to power off 7.913
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.748
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.205
And the file system changes introduced in version 6.3~testoverlayfs are present 0.396
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.014
And Tor is ready 11.838
Then the Upgrader considers the system as up-to-date 10.513
# 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.324
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:331 0.736
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
47.961
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.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
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 39.872
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.349
After features/support/hooks.rb:331 0.772
After features/support/hooks.rb:100 0.000