Project Number Date
test_Tails_ISO_21810-tca-vs-empty-bridge-strings 11 14 Oct 2026, 21:46

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 10:49.786 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:8.486
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.347
When I start Tails from USB drive "old" with network unplugged 51.418
Then the boot device has safe access rights 2.075
And Tails is running from USB drive "old" 0.166
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.168
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 3.582
After features/support/hooks.rb:108 0.057
Tags: @product
1:20.044
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 47.538
Then Tails is running from USB drive "old" 0.184
And I create a persistent partition 22.581
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 2.606
After features/support/hooks.rb:339 0.242
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.120
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 57.192
Then Tails is running from USB drive "old" 0.224
And all tps features are active 6.906
When I write some files expected to persist 0.893
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.118
And all persistence configuration files have safe access rights 0.271
And all persistent directories from the old Tails version have safe access rights 1.546
And I take note of which tps features are available 6.178
And I shutdown Tails and wait for the computer to power off 2.518
# 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.186
After features/support/hooks.rb:339 0.148
After features/support/hooks.rb:108 0.008
Tags: @product
2:11.044
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.362
And I log in to a new session 11.253
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.614
And I plug USB drive "to_upgrade" 2.605
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.853
Then the running Tails is installed on USB drive "to_upgrade" 17.119
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.752
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.010
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 59.676
Then all tps features from the old Tails version are active 0.911
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 1.907
And the expected persistent files created with the old Tails version are present in the filesystem 0.735
And all persistent directories from the old Tails version have safe access rights 1.500
After features/support/hooks.rb:339 0.630
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:19.473
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.907
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.195
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.184
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.298
When the network is plugged 0.035
And Tor is ready 12.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.856
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.337
Given I shutdown Tails and wait for the computer to power off 5.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.730
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.093
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.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.082
# 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.138
When the network is plugged 0.021
And Tor is ready 10.259
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.309
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.485
Given I shutdown Tails and wait for the computer to power off 2.519
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.769
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.782
And the file system changes introduced in version 6.3~testoverlayfs are present 0.269
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.103
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.047
And Tor is ready 10.072
Then the Upgrader considers the system as up-to-date 0.097
# 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.044
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.353
After features/support/hooks.rb:339 0.812
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.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 7.767
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.034
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 8.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.443
After features/support/hooks.rb:339 0.519
After features/support/hooks.rb:108 0.000