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

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:41.060 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.535
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.635
When I start Tails from USB drive "old" with network unplugged 58.629
Then the boot device has safe access rights 2.444
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.618
After features/support/hooks.rb:108 0.028
Tags: @product
1:22.801
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 48.792
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 23.838
And I take note of which tps features are available 6.627
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 2.596
After features/support/hooks.rb:339 0.536
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.763
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.252
Then Tails is running from USB drive "old" 0.183
And all tps features are active 8.486
When I write some files expected to persist 1.391
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 1.718
And I take note of which tps features are available 6.064
And I shutdown Tails and wait for the computer to power off 2.669
# 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.389
After features/support/hooks.rb:339 0.574
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.861
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.443
And I log in to a new session 12.067
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.721
And I plug USB drive "to_upgrade" 2.280
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.071
Then the running Tails is installed on USB drive "to_upgrade" 19.995
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 1.812
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.109
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.625
Then all tps features from the old Tails version are active 1.010
And Tails is running from USB drive "to_upgrade" 0.192
And the boot device has safe access rights 2.404
And the expected persistent files created with the old Tails version are present in the filesystem 1.085
And all persistent directories from the old Tails version have safe access rights 1.695
After features/support/hooks.rb:339 0.928
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
3:40.387
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.031
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.809
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.196
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.028
And Tor is ready 13.102
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.034
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.568
Given I shutdown Tails and wait for the computer to power off 6.498
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.036
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.095
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# 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.159
When the network is plugged 0.024
And Tor is ready 10.821
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.436
Given I shutdown Tails and wait for the computer to power off 4.124
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.444
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.026
And the file system changes introduced in version 6.3~testoverlayfs are present 0.350
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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.023
And Tor is ready 10.297
Then the Upgrader considers the system as up-to-date 0.103
# 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.893
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.486
After features/support/hooks.rb:339 1.106
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
18.601
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.142
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.071
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 8.322
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.751
After features/support/hooks.rb:339 0.615
After features/support/hooks.rb:108 0.000