Project Number Date
test_Tails_ISO_test-suite-tshark-leak-detection 5 17 Jun 2026, 10:56

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:28.671 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:6.870
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.558
When I start Tails from USB drive "old" with network unplugged 48.465
Then the boot device has safe access rights 2.903
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.285
After features/support/hooks.rb:339 3.783
After features/support/hooks.rb:108 0.025
Tags: @product
1:36.391
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 "old" with network unplugged and I login 58.006
Then Tails is running from USB drive "old" 0.317
And I create a persistent partition 24.498
And I take note of which tps features are available 4.460
Then a Tails persistence partition exists on USB drive "old" 0.595
And I shutdown Tails and wait for the computer to power off 8.452
After features/support/hooks.rb:339 0.555
After features/support/hooks.rb:108 0.017
Tags: @product
1:45.527
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.613
Then Tails is running from USB drive "old" 0.253
And all tps features are active 5.215
When I write some files expected to persist 1.497
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.325
And all persistent directories from the old Tails version have safe access rights 2.091
And I take note of which tps features are available 4.370
And I shutdown Tails and wait for the computer to power off 8.136
# 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.691
After features/support/hooks.rb:339 0.380
After features/support/hooks.rb:108 0.007
Tags: @product
2:12.465
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.853
And I log in to a new session 12.633
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.878
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.201
Then the running Tails is installed on USB drive "to_upgrade" 17.371
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 2.324
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.848
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.066
Then all tps features from the old Tails version are active 1.117
And Tails is running from USB drive "to_upgrade" 0.311
And the boot device has safe access rights 2.637
And the expected persistent files created with the old Tails version are present in the filesystem 1.367
And all persistent directories from the old Tails version have safe access rights 2.279
After features/support/hooks.rb:339 0.953
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
4:10.221
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 9.148
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.416
When the network is plugged 0.029
And Tor is ready 13.109
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.610
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.674
Given I shutdown Tails and wait for the computer to power off 11.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.919
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.814
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
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.128
# 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.294
When the network is plugged 0.017
And Tor is ready 9.894
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.521
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.765
Given I shutdown Tails and wait for the computer to power off 8.591
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.580
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.770
And the file system changes introduced in version 6.3~testoverlayfs are present 0.558
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.016
And Tor is ready 10.219
Then the Upgrader considers the system as up-to-date 10.540
# 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.718
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.425
After features/support/hooks.rb:339 0.731
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.346
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.599
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.053
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.380
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.985
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.000