Project Number Date
test_Tails_ISO_stable 6143 11 Feb 2026, 21:03

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:35.874 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:20.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 15.493
When I start Tails from USB drive "old" with network unplugged 59.185
Then the boot device has safe access rights 3.622
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 3.681
After features/support/hooks.rb:100 0.009
Tags: @product
1:37.981
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 1:0.461
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 28.352
And I take note of which tps features are available 0.913
Then a Tails persistence partition exists on USB drive "old" 0.757
And I shutdown Tails and wait for the computer to power off 7.101
After features/support/hooks.rb:331 0.452
After features/support/hooks.rb:100 0.011
Tags: @product
1:34.733
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.867
Then Tails is running from USB drive "old" 0.335
And all tps features are active 1.492
When I write some files expected to persist 1.566
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 2.401
And I take note of which tps features are available 0.231
And I shutdown Tails and wait for the computer to power off 4.109
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.987
After features/support/hooks.rb:331 0.206
After features/support/hooks.rb:100 0.008
Tags: @product
2:20.238
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 9.268
And I log in to a new session 13.301
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.057
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.337
Then the running Tails is installed on USB drive "to_upgrade" 18.670
And I unplug USB drive "to_upgrade" 0.181
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:331 0.754
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.435
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.907
Then all tps features from the old Tails version are active 1.615
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.396
And the expected persistent files created with the old Tails version are present in the filesystem 1.764
And all persistent directories from the old Tails version have safe access rights 2.335
After features/support/hooks.rb:331 0.836
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:1.963
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 with a persistent partition enabled and logged in 8.450
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.729
When the network is plugged 0.022
And Tor is ready 13.170
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.994
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.319
Given I shutdown Tails and wait for the computer to power off 7.139
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.729
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.597
And the file system changes introduced in version 6.2~testoverlayfs are present 0.342
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.378
When the network is plugged 0.018
And Tor is ready 11.504
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.845
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.990
Given I shutdown Tails and wait for the computer to power off 8.797
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.681
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.588
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.189
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.320
When the network is plugged 0.051
And Tor is ready 11.657
Then the Upgrader considers the system as up-to-date 10.622
# 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.974
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.407
After features/support/hooks.rb:331 0.960
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
21.416
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 8.500
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 10.535
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.962
After features/support/hooks.rb:331 0.827
After features/support/hooks.rb:100 0.000