Project Number Date
test_Tails_ISO_test-suite-tshark-leak-detection 11 19 Jun 2026, 12:42

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:57.810 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:17.127
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.526
When I start Tails from USB drive "old" with network unplugged 57.975
Then the boot device has safe access rights 2.713
And Tails is running from USB drive "old" 0.268
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.262
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:339 1.671
After features/support/hooks.rb:108 0.005
Tags: @product
1:39.406
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 59.485
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 25.976
And I take note of which tps features are available 4.666
Then a Tails persistence partition exists on USB drive "old" 0.588
And I shutdown Tails and wait for the computer to power off 8.335
After features/support/hooks.rb:339 0.479
After features/support/hooks.rb:108 0.008
Tags: @product
1:45.889
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.798
Then Tails is running from USB drive "old" 0.265
And all tps features are active 5.358
When I write some files expected to persist 1.437
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.161
And I take note of which tps features are available 4.903
And I shutdown Tails and wait for the computer to power off 8.335
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 13.023
After features/support/hooks.rb:339 0.491
After features/support/hooks.rb:108 0.009
Tags: @product
2:15.307
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.979
And I log in to a new session 14.656
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.987
And I plug USB drive "to_upgrade" 2.270
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.077
Then the running Tails is installed on USB drive "to_upgrade" 16.056
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:339 4.011
After features/support/hooks.rb:108 0.000
Tags: @product
1:19.210
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.334
Then all tps features from the old Tails version are active 1.120
And Tails is running from USB drive "to_upgrade" 0.281
And the boot device has safe access rights 2.799
And the expected persistent files created with the old Tails version are present in the filesystem 1.172
And all persistent directories from the old Tails version have safe access rights 2.442
After features/support/hooks.rb:339 0.527
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
4:17.851
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.553
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
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.339
When the network is plugged 0.016
And Tor is ready 13.294
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.819
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.482
Given I shutdown Tails and wait for the computer to power off 11.714
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.663
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 6.417
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.233
When the network is plugged 0.019
And Tor is ready 9.936
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.808
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.500
Given I shutdown Tails and wait for the computer to power off 8.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.172
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.801
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.017
And Tor is ready 10.613
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.924
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.687
After features/support/hooks.rb:339 0.745
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
23.017
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.311
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.681
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.639
After features/support/hooks.rb:339 0.860
After features/support/hooks.rb:108 0.000