Project Number Date
test_Tails_ISO_devel 4213 05 Feb 2026, 15:15

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:54.357 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:30.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.677
When I start Tails from USB drive "old" with network unplugged 1:10.577
Then the boot device has safe access rights 3.134
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.259
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 1.496
After features/support/hooks.rb:100 0.008
Tags: @product
1:27.194
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 56.594
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 24.297
And I take note of which tps features are available 0.847
Then a Tails persistence partition exists on USB drive "old" 0.584
And I shutdown Tails and wait for the computer to power off 4.464
After features/support/hooks.rb:331 0.212
After features/support/hooks.rb:100 0.009
Tags: @product
1:27.875
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.633
Then Tails is running from USB drive "old" 0.235
And all tps features are active 1.095
When I write some files expected to persist 1.384
# 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.336
And all persistent directories from the old Tails version have safe access rights 2.002
And I take note of which tps features are available 0.194
And I shutdown Tails and wait for the computer to power off 6.919
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.851
After features/support/hooks.rb:331 0.480
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.742
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.261
And I log in to a new session 12.833
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.932
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.937
Then the running Tails is installed on USB drive "to_upgrade" 17.226
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.159
After features/support/hooks.rb:331 0.920
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.337
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.062
Then all tps features from the old Tails version are active 0.913
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.663
And the expected persistent files created with the old Tails version are present in the filesystem 1.242
And all persistent directories from the old Tails version have safe access rights 2.106
After features/support/hooks.rb:331 1.002
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:28.493
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.931
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.364
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.321
When the network is plugged 0.017
And Tor is ready 14.960
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.656
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.960
Given I shutdown Tails and wait for the computer to power off 12.663
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.826
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.194
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.239
# 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.257
When the network is plugged 0.019
And Tor is ready 40.169
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.456
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.798
Given I shutdown Tails and wait for the computer to power off 8.064
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.939
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.435
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.193
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.021
And Tor is ready 9.775
Then the Upgrader considers the system as up-to-date 10.568
# 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.793
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:331 0.959
After features/support/hooks.rb:100 0.050
Tags: @product @automatic_upgrade
21.424
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 7.712
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.752
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.597
After features/support/hooks.rb:331 0.839
After features/support/hooks.rb:100 0.000