Project Number Date
test_Tails_ISO_devel 4445 13 Jun 2026, 11:18

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.295 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:10.127
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.171
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.027
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 51.686
Then the boot device has safe access rights 2.490
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.099
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 1.224
After features/support/hooks.rb:108 0.017
Tags: @product
1:31.412
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 52.293
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 25.117
And I take note of which tps features are available 4.490
Then a Tails persistence partition exists on USB drive "old" 0.577
And I shutdown Tails and wait for the computer to power off 8.544
After features/support/hooks.rb:339 0.445
After features/support/hooks.rb:108 0.019
Tags: @product
1:39.051
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.705
Then Tails is running from USB drive "old" 0.352
And all tps features are active 4.962
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.306
And all persistent directories from the old Tails version have safe access rights 1.849
And I take note of which tps features are available 4.038
And I shutdown Tails and wait for the computer to power off 7.057
# 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.202
After features/support/hooks.rb:339 0.312
After features/support/hooks.rb:108 0.018
Tags: @product
2:12.435
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.670
And I log in to a new session 11.945
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.719
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.173
Then the running Tails is installed on USB drive "to_upgrade" 16.401
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:339 1.910
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.878
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.109
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.455
Then all tps features from the old Tails version are active 1.085
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 2.537
And the expected persistent files created with the old Tails version are present in the filesystem 1.233
And all persistent directories from the old Tails version have safe access rights 2.178
After features/support/hooks.rb:339 0.859
After features/support/hooks.rb:108 0.018
Tags: @product @automatic_upgrade
4:4.003
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 with a persistent partition enabled and logged in 8.496
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
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.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.013
And Tor is ready 12.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.408
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.254
Given I shutdown Tails and wait for the computer to power off 10.044
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.145
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.692
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.228
When the network is plugged 0.016
And Tor is ready 10.109
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.750
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.478
Given I shutdown Tails and wait for the computer to power off 7.143
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.198
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.758
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
And only the 6.3~testoverlayfs SquashFS delta is installed 0.119
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.016
And Tor is ready 10.438
Then the Upgrader considers the system as up-to-date 10.610
# 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.525
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:339 0.969
After features/support/hooks.rb:108 0.037
Tags: @product @automatic_upgrade
21.386
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.545
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.092
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.053
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.318
After features/support/hooks.rb:339 0.847
After features/support/hooks.rb:108 0.000