Project Number Date
test_Tails_ISO_tails-circumvention-settings-developers-doc 1 25 Aug 2026, 18:44

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:21.115 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.342
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.524
When I start Tails from USB drive "old" with network unplugged 51.286
Then the boot device has safe access rights 1.814
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 1.705
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.313
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 "old" with network unplugged and I login 48.908
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 24.297
And I take note of which tps features are available 6.211
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 4.034
After features/support/hooks.rb:339 0.544
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.061
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.960
Then Tails is running from USB drive "old" 0.180
And all tps features are active 7.141
When I write some files expected to persist 1.020
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.298
And all persistent directories from the old Tails version have safe access rights 1.521
And I take note of which tps features are available 6.349
And I shutdown Tails and wait for the computer to power off 4.196
# 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.161
After features/support/hooks.rb:339 0.279
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.390
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.619
And I log in to a new session 11.826
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.592
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.352
Then the running Tails is installed on USB drive "to_upgrade" 18.456
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 1.755
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.814
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.174
Then all tps features from the old Tails version are active 1.144
And Tails is running from USB drive "to_upgrade" 0.265
And the boot device has safe access rights 2.276
And the expected persistent files created with the old Tails version are present in the filesystem 0.959
And all persistent directories from the old Tails version have safe access rights 1.906
After features/support/hooks.rb:339 0.847
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
3:32.225
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.342
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.178
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.280
When the network is plugged 0.035
And Tor is ready 13.498
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.912
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.993
Given I shutdown Tails and wait for the computer to power off 5.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.413
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 8.484
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.203
When the network is plugged 0.034
And Tor is ready 10.473
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.095
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.770
Given I shutdown Tails and wait for the computer to power off 4.133
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.828
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 8.135
And the file system changes introduced in version 6.3~testoverlayfs are present 0.341
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.029
And Tor is ready 10.736
Then the Upgrader considers the system as up-to-date 0.115
# 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.476
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.327
After features/support/hooks.rb:339 0.651
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.969
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 Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 10.117
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.468
After features/support/hooks.rb:339 0.741
After features/support/hooks.rb:108 0.000