Project Number Date
test_Tails_ISO_test-suite-tshark-leak-detection 10 18 Jun 2026, 12:29

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:50.164 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:14.321
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.090
When I start Tails from USB drive "old" with network unplugged 57.016
Then the boot device has safe access rights 2.511
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 1.377
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.456
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 51.368
Then Tails is running from USB drive "old" 0.217
And I create a persistent partition 24.292
And I take note of which tps features are available 3.840
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 8.093
After features/support/hooks.rb:339 0.427
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.550
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.279
Then Tails is running from USB drive "old" 0.227
And all tps features are active 4.639
When I write some files expected to persist 1.159
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.306
And all persistent directories from the old Tails version have safe access rights 1.896
And I take note of which tps features are available 3.697
And I shutdown Tails and wait for the computer to power off 8.249
# 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" 11.865
After features/support/hooks.rb:339 0.390
After features/support/hooks.rb:108 0.008
Tags: @product
2:9.730
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 without a persistent partition and stopped at Tails Greeter's login screen 7.824
And I log in to a new session 12.148
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.881
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.191
Then the running Tails is installed on USB drive "to_upgrade" 15.196
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 1.974
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.202
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.420
Then all tps features from the old Tails version are active 1.047
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 2.385
And the expected persistent files created with the old Tails version are present in the filesystem 1.046
And all persistent directories from the old Tails version have safe access rights 2.040
After features/support/hooks.rb:339 0.473
After features/support/hooks.rb:108 0.007
3:51.569
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.260
And no SquashFS delta is installed 0.054
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.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.372
When the network is plugged 0.019
And Tor is ready 13.337
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.197
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.072
Given I shutdown Tails and wait for the computer to power off 11.030
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.453
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 4.617
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
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.110
# 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.013
And Tor is ready 10.772
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.548
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.934
Given I shutdown Tails and wait for the computer to power off 7.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.566
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 4.709
And the file system changes introduced in version 6.3~testoverlayfs are present 0.368
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.016
And Tor is ready 10.849
Then the Upgrader considers the system as up-to-date 10.508
# 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.130
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.360
After features/support/hooks.rb:339 0.834
After features/support/hooks.rb:108 0.010
20.333
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.479
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
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.049
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.976
After features/support/hooks.rb:339 0.854
After features/support/hooks.rb:108 0.000