Project Number Date
test_Tails_ISO_stable 6115 03 Feb 2026, 12:14

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:48.864 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.254
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.367
When I start Tails from USB drive "old" with network unplugged 1:19.420
Then the boot device has safe access rights 2.688
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:331 1.597
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.393
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 55.153
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 23.662
And I take note of which tps features are available 0.761
Then a Tails persistence partition exists on USB drive "old" 0.554
And I shutdown Tails and wait for the computer to power off 7.954
After features/support/hooks.rb:331 0.463
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.346
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.678
Then Tails is running from USB drive "old" 0.370
And all tps features are active 1.210
When I write some files expected to persist 1.660
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 1.875
And I take note of which tps features are available 0.175
And I shutdown Tails and wait for the computer to power off 7.970
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.849
After features/support/hooks.rb:331 0.484
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.142
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 7.525
And I log in to a new session 12.726
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.794
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.042
Then the running Tails is installed on USB drive "to_upgrade" 16.515
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:331 3.846
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.374
Then all tps features from the old Tails version are active 1.163
And Tails is running from USB drive "to_upgrade" 0.289
And the boot device has safe access rights 2.637
And the expected persistent files created with the old Tails version are present in the filesystem 1.086
And all persistent directories from the old Tails version have safe access rights 2.540
After features/support/hooks.rb:331 0.579
After features/support/hooks.rb:100 0.006
4:22.696
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 8.722
And no SquashFS delta is installed 0.144
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.452
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.361
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.019
And Tor is ready 44.318
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.397
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.305
Given I shutdown Tails and wait for the computer to power off 18.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.454
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.191
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
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.128
# 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.200
When the network is plugged 0.014
And Tor is ready 10.084
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.440
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.619
Given I shutdown Tails and wait for the computer to power off 3.976
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.584
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.330
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.014
And Tor is ready 10.194
Then the Upgrader considers the system as up-to-date 10.692
# 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.858
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.420
After features/support/hooks.rb:331 1.025
After features/support/hooks.rb:100 0.011
20.857
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 7.511
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.308
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.669
After features/support/hooks.rb:331 0.934
After features/support/hooks.rb:100 0.000