Project Number Date
test_Tails_ISO_21810-tca-vs-empty-bridge-strings 1 05 Oct 2026, 14:12

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:45.330 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:15.321
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.582
When I start Tails from USB drive "old" with network unplugged 55.999
Then the boot device has safe access rights 2.960
And Tails is running from USB drive "old" 0.267
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.738
After features/support/hooks.rb:108 0.036
Tags: @product
1:24.424
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 49.081
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 23.914
And I take note of which tps features are available 6.621
Then a Tails persistence partition exists on USB drive "old" 0.496
And I shutdown Tails and wait for the computer to power off 3.941
After features/support/hooks.rb:339 0.432
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.066
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.414
Then Tails is running from USB drive "old" 0.237
And all tps features are active 8.293
When I write some files expected to persist 1.095
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.135
And all persistence configuration files have safe access rights 0.210
And all persistent directories from the old Tails version have safe access rights 1.644
And I take note of which tps features are available 6.217
And I shutdown Tails and wait for the computer to power off 4.152
# 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.570
After features/support/hooks.rb:339 0.291
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.767
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.943
And I log in to a new session 12.907
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.786
And I plug USB drive "to_upgrade" 2.275
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.002
Then the running Tails is installed on USB drive "to_upgrade" 19.588
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 3.905
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.140
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.965
Then all tps features from the old Tails version are active 1.285
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.638
And the expected persistent files created with the old Tails version are present in the filesystem 1.081
And all persistent directories from the old Tails version have safe access rights 1.835
After features/support/hooks.rb:339 0.608
After features/support/hooks.rb:108 0.006
3:41.600
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.517
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
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.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.024
And Tor is ready 13.099
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.006
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.384
Given I shutdown Tails and wait for the computer to power off 5.406
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.414
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.075
# 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.177
When the network is plugged 0.026
And Tor is ready 11.182
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.299
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.180
Given I shutdown Tails and wait for the computer to power off 4.004
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.255
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 9.248
And the file system changes introduced in version 6.3~testoverlayfs are present 0.413
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.028
And Tor is ready 11.173
Then the Upgrader considers the system as up-to-date 0.109
# 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 4.437
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.392
After features/support/hooks.rb:339 0.911
After features/support/hooks.rb:108 0.012
20.009
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.470
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.452
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.688
After features/support/hooks.rb:339 0.756
After features/support/hooks.rb:108 0.000