Project Number Date
test_Tails_ISO_stable 6446 15 Jun 2026, 14:42

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:34.899 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:3.256
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.154
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 14.137
When I start Tails from USB drive "old" with network unplugged 44.381
Then the boot device has safe access rights 2.814
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:339 1.491
After features/support/hooks.rb:108 0.022
Tags: @product
1:35.447
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.034
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 56.746
Then Tails is running from USB drive "old" 0.256
And I create a persistent partition 25.161
And I take note of which tps features are available 5.115
Then a Tails persistence partition exists on USB drive "old" 0.702
And I shutdown Tails and wait for the computer to power off 7.272
After features/support/hooks.rb:339 0.429
After features/support/hooks.rb:108 0.020
Tags: @product
1:42.462
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.139
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.261
Then Tails is running from USB drive "old" 0.301
And all tps features are active 5.647
When I write some files expected to persist 1.356
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 1.929
And I take note of which tps features are available 4.383
And I shutdown Tails and wait for the computer to power off 7.033
# 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.873
After features/support/hooks.rb:339 0.372
After features/support/hooks.rb:108 0.026
Tags: @product
2:14.682
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.022
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.471
And I log in to a new session 13.203
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.923
And I plug USB drive "to_upgrade" 2.311
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.566
Then the running Tails is installed on USB drive "to_upgrade" 16.946
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 0.928
After features/support/hooks.rb:108 0.000
Tags: @product
1:21.382
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.518
Then all tps features from the old Tails version are active 1.147
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 2.840
And the expected persistent files created with the old Tails version are present in the filesystem 1.302
And all persistent directories from the old Tails version have safe access rights 2.094
After features/support/hooks.rb:339 0.884
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
4:16.089
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.999
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.334
When the network is plugged 0.018
And Tor is ready 13.363
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.206
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.890
Given I shutdown Tails and wait for the computer to power off 10.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.176
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.603
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.183
# 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.290
When the network is plugged 0.024
And Tor is ready 9.919
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.107
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.016
Given I shutdown Tails and wait for the computer to power off 8.496
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.052
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 6.139
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.016
And Tor is ready 11.229
Then the Upgrader considers the system as up-to-date 10.565
# 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.863
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.400
After features/support/hooks.rb:339 0.800
After features/support/hooks.rb:108 0.039
Tags: @product @automatic_upgrade
21.578
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.938
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.237
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.012
After features/support/hooks.rb:339 0.656
After features/support/hooks.rb:108 0.000