Project Number Date
test_Tails_ISO_stable 6176 27 Feb 2026, 07:59

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 13:17.830 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:56.023
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.446
When I start Tails from USB drive "old" with network unplugged 1:38.093
Then the boot device has safe access rights 2.672
And Tails is running from USB drive "old" 0.265
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:331 1.442
After features/support/hooks.rb:100 0.008
Tags: @product
1:27.126
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 53.571
Then Tails is running from USB drive "old" 0.419
And I create a persistent partition 23.759
And I take note of which tps features are available 0.643
Then a Tails persistence partition exists on USB drive "old" 0.534
And I shutdown Tails and wait for the computer to power off 8.128
After features/support/hooks.rb:331 0.265
After features/support/hooks.rb:100 0.007
Tags: @product
1:19.725
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.659
Then Tails is running from USB drive "old" 0.242
And all tps features are active 0.989
When I write some files expected to persist 1.225
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 1.652
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 4.102
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.086
After features/support/hooks.rb:331 0.568
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.320
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.398
And I log in to a new session 13.477
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.780
And I plug USB drive "to_upgrade" 3.985
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.218
Then the running Tails is installed on USB drive "to_upgrade" 16.179
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:331 8.460
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.899
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.393
Then all tps features from the old Tails version are active 0.998
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 2.383
And the expected persistent files created with the old Tails version are present in the filesystem 1.047
And all persistent directories from the old Tails version have safe access rights 1.821
After features/support/hooks.rb:331 0.868
After features/support/hooks.rb:100 0.037
4:35.019
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 8.008
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.366
When the network is plugged 0.019
And Tor is ready 22.091
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.387
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.458
Given I shutdown Tails and wait for the computer to power off 20.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.683
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.060
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.216
When the network is plugged 0.019
And Tor is ready 21.572
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.353
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.604
Given I shutdown Tails and wait for the computer to power off 16.938
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.624
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.136
And the file system changes introduced in version 6.3~testoverlayfs are present 0.294
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.203
When the network is plugged 0.014
And Tor is ready 21.542
Then the Upgrader considers the system as up-to-date 0.097
# 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.541
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.414
After features/support/hooks.rb:331 0.964
After features/support/hooks.rb:100 0.010
27.714
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.246
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 19.800
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.343
After features/support/hooks.rb:331 1.345
After features/support/hooks.rb:100 0.000