Project Number Date
test_Tails_ISO_21810-tca-vs-empty-bridge-strings 2 05 Oct 2026, 21:53

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:44.295 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:9.502
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 14.205
When I start Tails from USB drive "old" with network unplugged 51.740
Then the boot device has safe access rights 1.868
And Tails is running from USB drive "old" 0.182
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.152
And I unplug USB drive "old" 0.102
After features/support/hooks.rb:339 3.568
After features/support/hooks.rb:108 0.058
Tags: @product
1:27.598
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 51.805
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 24.070
And I take note of which tps features are available 6.872
Then a Tails persistence partition exists on USB drive "old" 0.593
And I shutdown Tails and wait for the computer to power off 3.931
After features/support/hooks.rb:339 0.259
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.079
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.839
Then Tails is running from USB drive "old" 0.256
And all tps features are active 7.831
When I write some files expected to persist 1.463
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 1.965
And I take note of which tps features are available 7.135
And I shutdown Tails and wait for the computer to power off 3.878
# 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.035
After features/support/hooks.rb:339 0.271
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.580
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 without a persistent partition and stopped at Tails Greeter's login screen 8.693
And I log in to a new session 12.733
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.755
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.162
Then the running Tails is installed on USB drive "to_upgrade" 18.727
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.108
After features/support/hooks.rb:339 0.700
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.352
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.126
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.554
Then all tps features from the old Tails version are active 1.055
And Tails is running from USB drive "to_upgrade" 0.188
And the boot device has safe access rights 1.993
And the expected persistent files created with the old Tails version are present in the filesystem 0.847
And all persistent directories from the old Tails version have safe access rights 1.586
After features/support/hooks.rb:339 0.888
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:39.417
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.499
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.468
When the network is plugged 0.047
And Tor is ready 13.924
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.599
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.164
Given I shutdown Tails and wait for the computer to power off 6.706
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.868
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.919
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.190
When the network is plugged 0.033
And Tor is ready 11.066
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.332
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.145
Given I shutdown Tails and wait for the computer to power off 2.648
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.749
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.012
And the file system changes introduced in version 6.3~testoverlayfs are present 0.482
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.026
And Tor is ready 10.466
Then the Upgrader considers the system as up-to-date 0.090
# 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 3.214
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.312
After features/support/hooks.rb:339 0.988
After features/support/hooks.rb:108 0.068
Tags: @product @automatic_upgrade
19.764
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.208
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 10.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.997
After features/support/hooks.rb:339 0.959
After features/support/hooks.rb:108 0.000