Project Number Date
test_Tails_ISO_21810-tca-vs-empty-bridge-strings 9 12 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:11.866 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.315
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.363
When I start Tails from USB drive "old" with network unplugged 48.823
Then the boot device has safe access rights 2.358
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 1.213
After features/support/hooks.rb:108 0.006
Tags: @product
1:21.523
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.100
And I start Tails from USB drive "old" with network unplugged and I login 48.628
Then Tails is running from USB drive "old" 0.221
And I create a persistent partition 23.113
And I take note of which tps features are available 6.328
Then a Tails persistence partition exists on USB drive "old" 0.528
And I shutdown Tails and wait for the computer to power off 2.602
After features/support/hooks.rb:339 0.333
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.185
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.222
Then Tails is running from USB drive "old" 0.212
And all tps features are active 7.532
When I write some files expected to persist 1.085
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.569
And I take note of which tps features are available 5.886
And I shutdown Tails and wait for the computer to power off 2.532
# 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.605
After features/support/hooks.rb:339 0.167
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.318
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.293
And I log in to a new session 12.206
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.599
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.844
Then the running Tails is installed on USB drive "to_upgrade" 17.896
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.560
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.633
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.387
Then all tps features from the old Tails version are active 0.970
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.269
And the expected persistent files created with the old Tails version are present in the filesystem 0.991
And all persistent directories from the old Tails version have safe access rights 1.678
After features/support/hooks.rb:339 0.537
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:31.835
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 7.977
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.168
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.259
When the network is plugged 0.027
And Tor is ready 12.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.301
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.312
Given I shutdown Tails and wait for the computer to power off 5.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.361
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.341
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.114
# 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.263
When the network is plugged 0.029
And Tor is ready 11.112
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.324
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.565
Given I shutdown Tails and wait for the computer to power off 4.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.016
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.534
And the file system changes introduced in version 6.3~testoverlayfs are present 0.355
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.035
And Tor is ready 11.431
Then the Upgrader considers the system as up-to-date 0.124
# 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.742
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.369
After features/support/hooks.rb:339 1.017
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
18.055
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.938
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
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.035
And Tor is ready 9.508
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.304
After features/support/hooks.rb:339 0.594
After features/support/hooks.rb:108 0.000