Project Number Date
test_Tails_ISO_stable 6447 16 Jun 2026, 11: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 12:12.046 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:0.961
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.155
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 13.902
When I start Tails from USB drive "old" with network unplugged 42.336
Then the boot device has safe access rights 2.780
And Tails is running from USB drive "old" 0.265
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 1.223
After features/support/hooks.rb:108 0.017
Tags: @product
1:29.814
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.117
And I start Tails from USB drive "old" with network unplugged and I login 55.081
Then Tails is running from USB drive "old" 0.282
And I create a persistent partition 25.003
And I take note of which tps features are available 4.330
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 4.438
After features/support/hooks.rb:339 0.641
After features/support/hooks.rb:108 0.021
Tags: @product
1:43.973
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.021
Given a computer 0.165
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.012
Then Tails is running from USB drive "old" 0.220
And all tps features are active 5.143
When I write some files expected to persist 1.431
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.334
And all persistent directories from the old Tails version have safe access rights 1.997
And I take note of which tps features are available 4.699
And I shutdown Tails and wait for the computer to power off 8.677
# 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.126
After features/support/hooks.rb:339 0.405
After features/support/hooks.rb:108 0.019
Tags: @product
2:13.962
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.447
And I log in to a new session 13.895
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.938
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.017
Then the running Tails is installed on USB drive "to_upgrade" 16.159
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 2.100
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.499
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.141
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.072
Then all tps features from the old Tails version are active 1.040
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 2.707
And the expected persistent files created with the old Tails version are present in the filesystem 1.313
And all persistent directories from the old Tails version have safe access rights 1.964
After features/support/hooks.rb:339 0.834
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
4:6.296
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.058
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
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.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.407
When the network is plugged 0.019
And Tor is ready 13.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.130
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.372
Given I shutdown Tails and wait for the computer to power off 9.723
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.790
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.345
And the file system changes introduced in version 6.2~testoverlayfs are present 0.246
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.258
When the network is plugged 0.018
And Tor is ready 10.383
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.042
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.323
Given I shutdown Tails and wait for the computer to power off 7.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.455
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.242
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
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.180
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.028
And Tor is ready 10.068
Then the Upgrader considers the system as up-to-date 10.671
# 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.397
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:339 1.174
After features/support/hooks.rb:108 0.039
Tags: @product @automatic_upgrade
20.539
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.901
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 10.054
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.142
After features/support/hooks.rb:339 0.664
After features/support/hooks.rb:108 0.000