Project Number Date
test_Tails_ISO_web-release-7.14 4 29 Sep 2026, 20:36

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:12.217 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:26.851
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.102
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.033
When I start Tails from USB drive "old" with network unplugged 1:8.451
Then the boot device has safe access rights 2.545
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 3.743
After features/support/hooks.rb:108 0.048
Tags: @product
1:28.393
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login 51.190
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 23.594
And I take note of which tps features are available 7.461
Then a Tails persistence partition exists on USB drive "old" 0.586
And I shutdown Tails and wait for the computer to power off 5.232
After features/support/hooks.rb:339 0.447
After features/support/hooks.rb:108 0.006
Tags: @product
1:46.129
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.120
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.207
Then Tails is running from USB drive "old" 0.286
And all tps features are active 8.801
When I write some files expected to persist 1.308
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.087
And I take note of which tps features are available 8.913
And I shutdown Tails and wait for the computer to power off 4.181
# 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" 13.534
After features/support/hooks.rb:339 0.215
After features/support/hooks.rb:108 0.006
Tags: @product
2:19.097
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 9.154
And I log in to a new session 14.455
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.932
And I plug USB drive "to_upgrade" 2.284
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.841
Then the running Tails is installed on USB drive "to_upgrade" 20.160
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.479
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.132
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.227
Then all tps features from the old Tails version are active 1.186
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.502
And the expected persistent files created with the old Tails version are present in the filesystem 1.328
And all persistent directories from the old Tails version have safe access rights 1.888
After features/support/hooks.rb:339 0.702
After features/support/hooks.rb:108 0.008
3:38.644
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.628
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.282
When the network is plugged 0.037
And Tor is ready 13.034
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.960
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.685
Given I shutdown Tails and wait for the computer to power off 5.359
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.123
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.589
And the file system changes introduced in version 6.2~testoverlayfs are present 0.203
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.112
# 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.171
When the network is plugged 0.025
And Tor is ready 10.860
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.362
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.388
Given I shutdown Tails and wait for the computer to power off 4.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.546
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.355
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
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.088
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.028
And Tor is ready 10.201
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.565
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.777
After features/support/hooks.rb:108 0.011
19.621
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.453
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
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.070
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.524
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.304
After features/support/hooks.rb:339 0.584
After features/support/hooks.rb:108 0.000