Project Number Date
test_Tails_ISO_21810-tca-vs-empty-bridge-strings 7 10 Oct 2026, 21:45

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:33.874 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:22.557
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.033
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.521
When I start Tails from USB drive "old" with network unplugged 1:4.886
Then the boot device has safe access rights 2.187
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.076
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 3.709
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.498
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 48.819
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 24.410
And I take note of which tps features are available 6.535
Then a Tails persistence partition exists on USB drive "old" 0.520
And I shutdown Tails and wait for the computer to power off 3.890
After features/support/hooks.rb:339 0.325
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.860
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.005
Then Tails is running from USB drive "old" 0.219
And all tps features are active 6.985
When I write some files expected to persist 1.068
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.250
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 1.980
And I take note of which tps features are available 6.529
And I shutdown Tails and wait for the computer to power off 2.715
# 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.664
After features/support/hooks.rb:339 0.406
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.934
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.697
And I log in to a new session 13.105
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.722
And I plug USB drive "to_upgrade" 2.324
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.628
Then the running Tails is installed on USB drive "to_upgrade" 18.188
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.862
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.851
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.158
Then all tps features from the old Tails version are active 1.096
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.331
And the expected persistent files created with the old Tails version are present in the filesystem 1.184
And all persistent directories from the old Tails version have safe access rights 1.785
After features/support/hooks.rb:339 0.808
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
3:33.105
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.170
And no SquashFS delta is installed 0.048
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.159
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.244
When the network is plugged 0.025
And Tor is ready 12.905
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.943
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.099
Given I shutdown Tails and wait for the computer to power off 5.526
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.154
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.342
And the file system changes introduced in version 6.2~testoverlayfs are present 0.164
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.170
When the network is plugged 0.025
And Tor is ready 10.617
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.296
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.923
Given I shutdown Tails and wait for the computer to power off 3.981
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.852
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.140
And the file system changes introduced in version 6.3~testoverlayfs are present 0.322
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.145
When the network is plugged 0.032
And Tor is ready 10.199
Then the Upgrader considers the system as up-to-date 0.074
# 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.556
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.332
After features/support/hooks.rb:339 0.849
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.066
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.768
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 9.979
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.993
After features/support/hooks.rb:339 0.625
After features/support/hooks.rb:108 0.000