Project Number Date
test_Tails_ISO_21810-tca-vs-empty-bridge-strings 8 11 Oct 2026, 21:52

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:23.347 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:3.807
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.806
When I start Tails from USB drive "old" with network unplugged 45.673
Then the boot device has safe access rights 2.602
And Tails is running from USB drive "old" 0.183
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.105
After features/support/hooks.rb:339 3.742
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.139
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 49.488
Then Tails is running from USB drive "old" 0.343
And I create a persistent partition 25.607
And I take note of which tps features are available 6.929
Then a Tails persistence partition exists on USB drive "old" 0.564
And I shutdown Tails and wait for the computer to power off 4.107
After features/support/hooks.rb:339 0.254
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.192
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.044
Then Tails is running from USB drive "old" 0.275
And all tps features are active 7.773
When I write some files expected to persist 1.270
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 1.509
And I take note of which tps features are available 6.226
And I shutdown Tails and wait for the computer to power off 3.811
# 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.682
After features/support/hooks.rb:339 0.145
After features/support/hooks.rb:108 0.008
Tags: @product
2:14.568
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 8.813
And I log in to a new session 12.644
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.699
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.139
Then the running Tails is installed on USB drive "to_upgrade" 18.798
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.108
After features/support/hooks.rb:339 2.198
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.784
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.105
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.795
Then all tps features from the old Tails version are active 1.119
And Tails is running from USB drive "to_upgrade" 0.203
And the boot device has safe access rights 2.270
And the expected persistent files created with the old Tails version are present in the filesystem 1.251
And all persistent directories from the old Tails version have safe access rights 2.038
After features/support/hooks.rb:339 1.031
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:30.577
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.397
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.277
When the network is plugged 0.030
And Tor is ready 11.807
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.026
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.777
Given I shutdown Tails and wait for the computer to power off 5.255
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.757
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.851
And the file system changes introduced in version 6.2~testoverlayfs are present 0.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.200
When the network is plugged 0.032
And Tor is ready 10.677
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.008
Given I shutdown Tails and wait for the computer to power off 4.148
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.017
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.307
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.031
And Tor is ready 10.696
Then the Upgrader considers the system as up-to-date 0.086
# 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.159
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.338
After features/support/hooks.rb:339 0.718
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
19.277
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.968
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.949
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.899
After features/support/hooks.rb:339 0.877
After features/support/hooks.rb:108 0.000