Project Number Date
test_Tails_ISO_21578-test-suite-pure-disk-boot 1 15 Jun 2026, 16: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 13:10.687 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:20.622
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 14.120
When I start Tails from USB drive "old" with network unplugged 1:1.557
Then the boot device has safe access rights 2.913
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:339 3.465
After features/support/hooks.rb:108 0.028
Tags: @product
1:37.284
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 58.563
Then Tails is running from USB drive "old" 0.253
And I create a persistent partition 27.256
And I take note of which tps features are available 5.538
Then a Tails persistence partition exists on USB drive "old" 0.656
And I shutdown Tails and wait for the computer to power off 4.826
After features/support/hooks.rb:339 0.585
After features/support/hooks.rb:108 0.026
Tags: @product
1:49.386
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.025
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.844
Then Tails is running from USB drive "old" 0.329
And all tps features are active 6.514
When I write some files expected to persist 1.357
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 1.998
And I take note of which tps features are available 4.923
And I shutdown Tails and wait for the computer to power off 8.139
# 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.601
After features/support/hooks.rb:339 0.552
After features/support/hooks.rb:108 0.031
Tags: @product
2:15.306
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.658
And I log in to a new session 14.239
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.037
And I plug USB drive "to_upgrade" 2.260
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.152
Then the running Tails is installed on USB drive "to_upgrade" 16.625
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:339 2.150
After features/support/hooks.rb:108 0.000
Tags: @product
1:21.351
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.044
Given a computer 0.320
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.030
Then all tps features from the old Tails version are active 1.043
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.855
And the expected persistent files created with the old Tails version are present in the filesystem 1.299
And all persistent directories from the old Tails version have safe access rights 2.557
After features/support/hooks.rb:339 1.067
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
4:23.358
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.026
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.457
And no SquashFS delta is installed 0.083
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.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.018
And Tor is ready 13.047
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.414
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.833
Given I shutdown Tails and wait for the computer to power off 10.552
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.001
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 5.974
And the file system changes introduced in version 6.2~testoverlayfs are present 0.252
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.189
# 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.276
When the network is plugged 0.020
And Tor is ready 10.086
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.775
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.218
Given I shutdown Tails and wait for the computer to power off 7.096
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.537
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.671
And the file system changes introduced in version 6.3~testoverlayfs are present 0.472
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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.022
And Tor is ready 11.554
Then the Upgrader considers the system as up-to-date 10.607
# 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 5.150
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.563
After features/support/hooks.rb:339 1.168
After features/support/hooks.rb:108 0.079
Tags: @product @automatic_upgrade
23.377
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.586
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.833
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.529
After features/support/hooks.rb:339 0.836
After features/support/hooks.rb:108 0.000