Project Number Date
test_Tails_ISO_stable 6248 30 Mar 2026, 15:02

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:47.937 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:48.152
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.061
When I start Tails from USB drive "old" with network unplugged 1:29.438
Then the boot device has safe access rights 2.789
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 1.464
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.231
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 56.864
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 24.405
And I take note of which tps features are available 0.767
Then a Tails persistence partition exists on USB drive "old" 0.540
And I shutdown Tails and wait for the computer to power off 8.291
After features/support/hooks.rb:331 0.174
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.714
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.396
Then Tails is running from USB drive "old" 0.318
And all tps features are active 1.239
When I write some files expected to persist 1.387
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.445
And all persistent directories from the old Tails version have safe access rights 1.996
And I take note of which tps features are available 0.217
And I shutdown Tails and wait for the computer to power off 8.269
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.206
After features/support/hooks.rb:331 0.318
After features/support/hooks.rb:100 0.006
Tags: @product
2:19.426
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.401
And I log in to a new session 17.957
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.680
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.419
Then the running Tails is installed on USB drive "to_upgrade" 17.314
And I unplug USB drive "to_upgrade" 0.167
And I unplug USB drive "__internal" 0.267
After features/support/hooks.rb:331 2.878
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.923
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.253
Then all tps features from the old Tails version are active 1.309
And Tails is running from USB drive "to_upgrade" 0.263
And the boot device has safe access rights 2.688
And the expected persistent files created with the old Tails version are present in the filesystem 1.246
And all persistent directories from the old Tails version have safe access rights 2.113
After features/support/hooks.rb:331 0.879
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:57.478
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.490
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.024
And Tor is ready 28.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.371
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.728
Given I shutdown Tails and wait for the computer to power off 20.572
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.539
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.181
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.193
When the network is plugged 0.018
And Tor is ready 22.285
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.365
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.823
Given I shutdown Tails and wait for the computer to power off 17.512
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.511
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.136
And the file system changes introduced in version 6.3~testoverlayfs are present 0.431
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.236
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.019
And Tor is ready 20.616
Then the Upgrader considers the system as up-to-date 0.100
# 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.332
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.421
After features/support/hooks.rb:331 1.102
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
29.009
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.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.337
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 19.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.421
After features/support/hooks.rb:331 0.888
After features/support/hooks.rb:100 0.000