Project Number Date
test_Tails_ISO_devel 4464 22 Jun 2026, 11:35

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:44.633 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.209
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given a computer 0.151
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 13.932
When I start Tails from USB drive "old" with network unplugged 55.717
Then the boot device has safe access rights 2.614
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.464
After features/support/hooks.rb:108 0.025
Tags: @product
1:38.729
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.027
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 59.288
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 26.158
And I take note of which tps features are available 4.853
Then a Tails persistence partition exists on USB drive "old" 0.658
And I shutdown Tails and wait for the computer to power off 7.289
After features/support/hooks.rb:339 0.174
After features/support/hooks.rb:108 0.017
Tags: @product
1:43.625
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given a computer 0.124
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.620
Then Tails is running from USB drive "old" 0.277
And all tps features are active 5.296
When I write some files expected to persist 1.363
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.302
And all persistent directories from the old Tails version have safe access rights 1.762
And I take note of which tps features are available 4.363
And I shutdown Tails and wait for the computer to power off 7.282
# 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.064
After features/support/hooks.rb:339 0.190
After features/support/hooks.rb:108 0.020
Tags: @product
2:14.839
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.049
And I log in to a new session 12.588
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.125
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.481
Then the running Tails is installed on USB drive "to_upgrade" 17.100
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 2.141
After features/support/hooks.rb:108 0.000
Tags: @product
1:20.082
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.023
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.386
Then all tps features from the old Tails version are active 1.308
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.719
And the expected persistent files created with the old Tails version are present in the filesystem 1.178
And all persistent directories from the old Tails version have safe access rights 2.082
After features/support/hooks.rb:339 0.768
After features/support/hooks.rb:108 0.051
Tags: @product @automatic_upgrade
4:12.650
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.973
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.032
And Tor is ready 13.069
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.604
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.873
Given I shutdown Tails and wait for the computer to power off 9.780
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.958
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.285
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
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.145
# 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.214
When the network is plugged 0.026
And Tor is ready 12.069
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.030
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.875
Given I shutdown Tails and wait for the computer to power off 8.966
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.203
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.957
And the file system changes introduced in version 6.3~testoverlayfs are present 0.455
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.018
And Tor is ready 10.248
Then the Upgrader considers the system as up-to-date 10.616
# 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.962
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:339 0.786
After features/support/hooks.rb:108 0.044
Tags: @product @automatic_upgrade
20.496
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.653
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.312
After features/support/hooks.rb:339 0.722
After features/support/hooks.rb:108 0.000