Project Number Date
test_Tails_ISO_21810-tca-vs-empty-bridge-strings 6 09 Oct 2026, 21:48

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:16.440 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:14.430
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.651
When I start Tails from USB drive "old" with network unplugged 56.623
Then the boot device has safe access rights 2.357
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.161
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:339 3.642
After features/support/hooks.rb:108 0.047
Tags: @product
1:21.866
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 47.652
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 23.049
And I take note of which tps features are available 6.357
Then a Tails persistence partition exists on USB drive "old" 0.491
And I shutdown Tails and wait for the computer to power off 4.004
After features/support/hooks.rb:339 0.531
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.783
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.499
Then Tails is running from USB drive "old" 0.173
And all tps features are active 7.289
When I write some files expected to persist 1.133
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.330
And all persistent directories from the old Tails version have safe access rights 1.618
And I take note of which tps features are available 6.203
And I shutdown Tails and wait for the computer to power off 2.570
# 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.715
After features/support/hooks.rb:339 0.553
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.325
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.377
And I log in to a new session 13.064
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.620
And I plug USB drive "to_upgrade" 2.172
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.640
Then the running Tails is installed on USB drive "to_upgrade" 18.222
And I unplug USB drive "to_upgrade" 0.107
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 2.090
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.462
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.104
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.327
Then all tps features from the old Tails version are active 1.099
And Tails is running from USB drive "to_upgrade" 0.194
And the boot device has safe access rights 2.201
And the expected persistent files created with the old Tails version are present in the filesystem 1.010
And all persistent directories from the old Tails version have safe access rights 1.523
After features/support/hooks.rb:339 0.702
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:28.258
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.866
And no SquashFS delta is installed 0.054
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.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.185
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.031
And Tor is ready 13.027
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.329
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.148
Given I shutdown Tails and wait for the computer to power off 5.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.992
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.133
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
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.102
# 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.161
When the network is plugged 0.026
And Tor is ready 10.654
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.301
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.550
Given I shutdown Tails and wait for the computer to power off 2.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.186
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.244
And the file system changes introduced in version 6.3~testoverlayfs are present 0.286
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.040
And Tor is ready 10.750
Then the Upgrader considers the system as up-to-date 0.095
# 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.666
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.300
After features/support/hooks.rb:339 0.662
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.312
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.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 8.266
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.642
After features/support/hooks.rb:339 0.882
After features/support/hooks.rb:108 0.000