Project Number Date
test_Tails_ISO_stable 6085 22 Jan 2026, 15:34

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 11:6.274 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:9.298
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 13.603
When I start Tails from USB drive "old" with network unplugged 51.144
Then the boot device has safe access rights 2.708
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.030
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:331 3.879
After features/support/hooks.rb:100 0.024
Tags: @product
1:22.128
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 52.587
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 23.745
And I take note of which tps features are available 0.747
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 4.269
After features/support/hooks.rb:331 0.269
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.241
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.064
Then Tails is running from USB drive "old" 0.259
And all tps features are active 1.094
When I write some files expected to persist 1.251
# 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.308
And all persistent directories from the old Tails version have safe access rights 1.771
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 8.235
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.873
After features/support/hooks.rb:331 0.624
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.351
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 without a persistent partition and stopped at Tails Greeter's login screen 8.801
And I log in to a new session 10.928
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.853
And I plug USB drive "to_upgrade" 2.306
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.386
Then the running Tails is installed on USB drive "to_upgrade" 15.802
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 3.793
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.304
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.619
Then all tps features from the old Tails version are active 0.841
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 2.500
And the expected persistent files created with the old Tails version are present in the filesystem 1.229
And all persistent directories from the old Tails version have safe access rights 1.820
After features/support/hooks.rb:331 0.951
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
3:32.139
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.231
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
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.178
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.017
And Tor is ready 13.177
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.407
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.465
Given I shutdown Tails and wait for the computer to power off 6.940
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.831
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.104
And the file system changes introduced in version 6.2~testoverlayfs are present 0.286
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# 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.212
When the network is plugged 0.014
And Tor is ready 9.640
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.404
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.069
Given I shutdown Tails and wait for the computer to power off 8.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.421
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 1.106
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.020
And Tor is ready 10.020
Then the Upgrader considers the system as up-to-date 10.464
# 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 3.736
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.417
After features/support/hooks.rb:331 0.693
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
19.812
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.276
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
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.018
And Tor is ready 9.744
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.403
After features/support/hooks.rb:331 0.934
After features/support/hooks.rb:100 0.000