Project Number Date
test_Tails_ISO_21171-trixie-13.6 3 13 Jul 2026, 18:04

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 12:23.796 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:12.971
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 13.591
When I start Tails from USB drive "old" with network unplugged 55.092
Then the boot device has safe access rights 2.519
And Tails is running from USB drive "old" 0.215
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:339 3.613
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.180
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 55.248
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 25.682
And I take note of which tps features are available 4.529
Then a Tails persistence partition exists on USB drive "old" 0.551
And I shutdown Tails and wait for the computer to power off 6.877
After features/support/hooks.rb:339 0.239
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.381
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.161
Then Tails is running from USB drive "old" 0.400
And all tps features are active 5.511
When I write some files expected to persist 1.403
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.351
And all persistent directories from the old Tails version have safe access rights 2.077
And I take note of which tps features are available 3.723
And I shutdown Tails and wait for the computer to power off 8.169
# 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.357
After features/support/hooks.rb:339 0.448
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.588
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.094
And I log in to a new session 12.430
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.936
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.826
Then the running Tails is installed on USB drive "to_upgrade" 14.807
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.036
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.755
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.119
Then all tps features from the old Tails version are active 0.975
And Tails is running from USB drive "to_upgrade" 0.233
And the boot device has safe access rights 2.810
And the expected persistent files created with the old Tails version are present in the filesystem 1.368
And all persistent directories from the old Tails version have safe access rights 2.197
After features/support/hooks.rb:339 0.998
After features/support/hooks.rb:108 0.007
4:8.544
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.659
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.022
And Tor is ready 14.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.378
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.044
Given I shutdown Tails and wait for the computer to power off 11.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.603
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 6.129
And the file system changes introduced in version 6.2~testoverlayfs are present 0.312
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.181
# 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.225
When the network is plugged 0.022
And Tor is ready 10.683
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.806
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.908
Given I shutdown Tails and wait for the computer to power off 8.144
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.157
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.568
And the file system changes introduced in version 6.3~testoverlayfs are present 0.395
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.017
And Tor is ready 9.796
Then the Upgrader considers the system as up-to-date 10.676
# 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.183
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:339 1.006
After features/support/hooks.rb:108 0.036
19.374
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 7.363
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.077
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.870
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.712
After features/support/hooks.rb:339 0.849
After features/support/hooks.rb:108 0.000