Project Number Date
test_Tails_ISO_devel 4652 01 Oct 2026, 17:31

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:16.935 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.129
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.716
When I start Tails from USB drive "old" with network unplugged 53.326
Then the boot device has safe access rights 2.294
And Tails is running from USB drive "old" 0.265
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 3.410
After features/support/hooks.rb:108 0.061
Tags: @product
1:26.821
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login 50.529
Then Tails is running from USB drive "old" 0.217
And I create a persistent partition 24.479
And I take note of which tps features are available 7.031
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 3.896
After features/support/hooks.rb:339 0.553
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.423
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.277
Then Tails is running from USB drive "old" 0.167
And all tps features are active 7.657
When I write some files expected to persist 1.378
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 1.752
And I take note of which tps features are available 5.672
And I shutdown Tails and wait for the computer to power off 2.647
# 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.290
After features/support/hooks.rb:339 0.383
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.394
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 without a persistent partition and stopped at Tails Greeter's login screen 8.466
And I log in to a new session 13.600
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.711
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.930
Then the running Tails is installed on USB drive "to_upgrade" 19.206
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 1.850
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.647
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.595
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.491
Then all tps features from the old Tails version are active 1.044
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.372
And the expected persistent files created with the old Tails version are present in the filesystem 1.231
And all persistent directories from the old Tails version have safe access rights 1.697
After features/support/hooks.rb:339 0.582
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:48.855
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.426
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.180
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.303
When the network is plugged 0.030
And Tor is ready 11.826
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.986
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.800
Given I shutdown Tails and wait for the computer to power off 5.490
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.150
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.916
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.173
When the network is plugged 0.035
And Tor is ready 10.831
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.980
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.976
Given I shutdown Tails and wait for the computer to power off 4.015
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.494
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.429
And the file system changes introduced in version 6.3~testoverlayfs are present 0.321
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.144
When the network is plugged 0.032
And Tor is ready 10.289
Then the Upgrader considers the system as up-to-date 0.106
# 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 3.694
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.307
After features/support/hooks.rb:339 1.344
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
45.662
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 34.725
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.066
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 8.921
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.615
After features/support/hooks.rb:339 0.477
After features/support/hooks.rb:108 0.000