Project Number Date
test_Tails_ISO_stable 6313 21 Apr 2026, 07:22

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:33.766 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:1.642
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.458
When I start Tails from USB drive "old" with network unplugged 42.780
Then the boot device has safe access rights 2.593
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.544
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.169
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 55.308
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 25.836
And I take note of which tps features are available 0.716
Then a Tails persistence partition exists on USB drive "old" 0.671
And I shutdown Tails and wait for the computer to power off 8.334
After features/support/hooks.rb:331 0.235
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.873
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.643
Then Tails is running from USB drive "old" 0.298
And all tps features are active 1.071
When I write some files expected to persist 1.192
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.138
And all persistence configuration files have safe access rights 0.405
And all persistent directories from the old Tails version have safe access rights 1.943
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 8.567
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.393
After features/support/hooks.rb:331 0.505
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.311
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 8.009
And I log in to a new session 11.798
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.780
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.717
Then the running Tails is installed on USB drive "to_upgrade" 16.484
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 2.057
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.340
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.693
Then all tps features from the old Tails version are active 1.231
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.781
And the expected persistent files created with the old Tails version are present in the filesystem 1.214
And all persistent directories from the old Tails version have safe access rights 2.094
After features/support/hooks.rb:331 0.919
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:42.233
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.981
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.368
When the network is plugged 0.032
And Tor is ready 21.111
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.476
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.305
Given I shutdown Tails and wait for the computer to power off 20.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.865
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 1.221
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.228
When the network is plugged 0.015
And Tor is ready 20.585
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.367
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.678
Given I shutdown Tails and wait for the computer to power off 17.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.455
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.259
And the file system changes introduced in version 6.3~testoverlayfs are present 0.530
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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.017
And Tor is ready 20.816
Then the Upgrader considers the system as up-to-date 0.108
# 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.404
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:331 0.803
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
26.195
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.826
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 17.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.356
After features/support/hooks.rb:331 1.009
After features/support/hooks.rb:100 0.000