Project Number Date
test_Tails_ISO_stable 6490 06 Jul 2026, 11:47

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:7.539 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.950
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 14.130
When I start Tails from USB drive "old" with network unplugged 54.398
Then the boot device has safe access rights 2.546
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 3.664
After features/support/hooks.rb:108 0.007
Tags: @product
1:28.736
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 53.886
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 25.536
And I take note of which tps features are available 3.972
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 4.463
After features/support/hooks.rb:339 0.125
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.907
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.799
Then Tails is running from USB drive "old" 0.282
And all tps features are active 5.441
When I write some files expected to persist 1.318
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.341
And all persistent directories from the old Tails version have safe access rights 1.860
And I take note of which tps features are available 4.169
And I shutdown Tails and wait for the computer to power off 4.070
# 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.403
After features/support/hooks.rb:339 0.469
After features/support/hooks.rb:108 0.008
Tags: @product
2:10.453
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.001
And I log in to a new session 11.661
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.783
And I plug USB drive "to_upgrade" 2.188
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.727
Then the running Tails is installed on USB drive "to_upgrade" 15.754
And I unplug USB drive "to_upgrade" 0.179
And I unplug USB drive "__internal" 0.157
After features/support/hooks.rb:339 2.139
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.493
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.352
Then all tps features from the old Tails version are active 1.032
And Tails is running from USB drive "to_upgrade" 0.265
And the boot device has safe access rights 2.521
And the expected persistent files created with the old Tails version are present in the filesystem 1.246
And all persistent directories from the old Tails version have safe access rights 2.013
After features/support/hooks.rb:339 0.761
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:2.171
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.437
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.372
When the network is plugged 0.012
And Tor is ready 14.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.003
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.966
Given I shutdown Tails and wait for the computer to power off 11.320
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.429
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 5.765
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.179
# 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.243
When the network is plugged 0.019
And Tor is ready 9.937
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.285
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.552
Given I shutdown Tails and wait for the computer to power off 7.180
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.947
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 4.935
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.015
And Tor is ready 11.182
Then the Upgrader considers the system as up-to-date 10.586
# 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.280
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:339 0.852
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.826
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 7.553
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 9.989
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.884
After features/support/hooks.rb:339 0.934
After features/support/hooks.rb:108 0.000