Project Number Date
test_Tails_ISO_21810-tca-vs-empty-bridge-strings 3 06 Oct 2026, 22:15

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:2.197 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:16.731
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.899
When I start Tails from USB drive "old" with network unplugged 58.798
Then the boot device has safe access rights 2.370
And Tails is running from USB drive "old" 0.178
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.135
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.132
After features/support/hooks.rb:108 0.010
Tags: @product
1:25.252
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 49.398
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 24.381
And I take note of which tps features are available 6.415
Then a Tails persistence partition exists on USB drive "old" 0.534
And I shutdown Tails and wait for the computer to power off 4.196
After features/support/hooks.rb:339 0.582
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.807
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.302
Then Tails is running from USB drive "old" 0.223
And all tps features are active 7.651
When I write some files expected to persist 1.325
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.105
And all persistence configuration files have safe access rights 0.259
And all persistent directories from the old Tails version have safe access rights 1.916
And I take note of which tps features are available 6.672
And I shutdown Tails and wait for the computer to power off 2.621
# 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.617
After features/support/hooks.rb:339 0.482
After features/support/hooks.rb:108 0.005
Tags: @product
2:41.617
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 35.447
And I log in to a new session 12.036
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.963
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.662
Then the running Tails is installed on USB drive "to_upgrade" 19.056
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 1.990
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.595
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.631
Then all tps features from the old Tails version are active 1.242
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.585
And the expected persistent files created with the old Tails version are present in the filesystem 1.113
And all persistent directories from the old Tails version have safe access rights 1.711
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:33.587
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 8.035
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.378
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.284
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.324
When the network is plugged 0.025
And Tor is ready 12.582
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.076
Given I shutdown Tails and wait for the computer to power off 6.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.436
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.514
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.104
# 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.164
When the network is plugged 0.025
And Tor is ready 10.922
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.334
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.552
Given I shutdown Tails and wait for the computer to power off 3.934
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.659
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.430
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.161
When the network is plugged 0.026
And Tor is ready 11.019
Then the Upgrader considers the system as up-to-date 0.168
# 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.684
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.335
After features/support/hooks.rb:339 0.785
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.605
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 8.311
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
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.032
And Tor is ready 10.555
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.349
After features/support/hooks.rb:339 0.545
After features/support/hooks.rb:108 0.000