Project Number Date
test_Tails_ISO_test-suite-tshark-leak-detection 12 20 Jun 2026, 12:41

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:12.353 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:10.649
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.094
When I start Tails from USB drive "old" with network unplugged 51.650
Then the boot device has safe access rights 3.056
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:339 3.451
After features/support/hooks.rb:108 0.051
Tags: @product
1:34.052
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 56.361
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 24.294
And I take note of which tps features are available 4.202
Then a Tails persistence partition exists on USB drive "old" 0.570
And I shutdown Tails and wait for the computer to power off 8.249
After features/support/hooks.rb:339 0.419
After features/support/hooks.rb:108 0.006
Tags: @product
1:42.068
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.310
Then Tails is running from USB drive "old" 0.267
And all tps features are active 5.475
When I write some files expected to persist 1.456
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 2.062
And I take note of which tps features are available 4.352
And I shutdown Tails and wait for the computer to power off 8.284
# 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" 12.310
After features/support/hooks.rb:339 0.324
After features/support/hooks.rb:108 0.008
Tags: @product
2:13.032
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 without a persistent partition and stopped at Tails Greeter's login screen 8.384
And I log in to a new session 13.387
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.875
And I plug USB drive "to_upgrade" 2.214
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.358
Then the running Tails is installed on USB drive "to_upgrade" 15.532
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 3.603
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.724
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.664
Then all tps features from the old Tails version are active 0.976
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 2.579
And the expected persistent files created with the old Tails version are present in the filesystem 1.140
And all persistent directories from the old Tails version have safe access rights 2.029
After features/support/hooks.rb:339 1.057
After features/support/hooks.rb:108 0.013
3:59.123
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.896
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.015
And Tor is ready 14.149
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.749
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.463
Given I shutdown Tails and wait for the computer to power off 6.716
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.656
Then Tails is running version 6.2~testoverlayfs 0.029
And all tps features are active 5.750
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.191
When the network is plugged 0.013
And Tor is ready 11.381
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.459
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.361
Given I shutdown Tails and wait for the computer to power off 7.927
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.523
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.128
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.016
And Tor is ready 10.256
Then the Upgrader considers the system as up-to-date 10.542
# 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.241
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.403
After features/support/hooks.rb:339 0.789
After features/support/hooks.rb:108 0.011
19.702
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 7.784
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
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.016
And Tor is ready 9.689
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.836
After features/support/hooks.rb:339 1.084
After features/support/hooks.rb:108 0.000