Project Number Date
test_Tails_ISO_devel 4529 04 Aug 2026, 11:37

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 11:49.128 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:11.475
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.044
And I create a 7200 MiB disk named "old" 0.006
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.785
When I start Tails from USB drive "old" with network unplugged 53.287
Then the boot device has safe access rights 2.637
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:339 3.896
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.589
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login 53.756
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 24.901
And I take note of which tps features are available 4.130
Then a Tails persistence partition exists on USB drive "old" 0.509
And I shutdown Tails and wait for the computer to power off 3.997
After features/support/hooks.rb:339 0.278
After features/support/hooks.rb:108 0.007
Tags: @product
1:34.019
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.878
Then Tails is running from USB drive "old" 0.306
And all tps features are active 5.081
When I write some files expected to persist 1.384
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.226
And all persistence configuration files have safe access rights 0.294
And all persistent directories from the old Tails version have safe access rights 2.003
And I take note of which tps features are available 3.817
And I shutdown Tails and wait for the computer to power off 5.543
# 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.404
After features/support/hooks.rb:339 0.277
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.005
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.072
And I log in to a new session 12.612
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.707
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.756
Then the running Tails is installed on USB drive "to_upgrade" 14.329
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 2.441
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.792
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.356
Then all tps features from the old Tails version are active 0.893
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.312
And the expected persistent files created with the old Tails version are present in the filesystem 1.027
And all persistent directories from the old Tails version have safe access rights 1.894
After features/support/hooks.rb:339 0.971
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:52.312
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.055
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.374
When the network is plugged 0.013
And Tor is ready 13.386
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.941
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.570
Given I shutdown Tails and wait for the computer to power off 5.453
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.724
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.246
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.212
# 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.189
When the network is plugged 0.017
And Tor is ready 10.729
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.048
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.422
Given I shutdown Tails and wait for the computer to power off 4.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.773
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.747
And the file system changes introduced in version 6.3~testoverlayfs are present 0.325
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.240
When the network is plugged 0.018
And Tor is ready 10.070
Then the Upgrader considers the system as up-to-date 10.574
# 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.272
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.487
After features/support/hooks.rb:339 0.662
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
20.932
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.433
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
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.054
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.407
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.741
After features/support/hooks.rb:339 0.841
After features/support/hooks.rb:108 0.000