Project Number Date
test_Tails_ISO_devel 4415 26 May 2026, 11:14

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:45.197 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:14.423
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.015
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 13.944
When I start Tails from USB drive "old" with network unplugged 55.308
Then the boot device has safe access rights 3.161
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.221
After features/support/hooks.rb:335 1.929
After features/support/hooks.rb:104 0.008
Tags: @product
1:32.922
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 57.615
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 25.106
And I take note of which tps features are available 1.121
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 8.116
After features/support/hooks.rb:335 0.398
After features/support/hooks.rb:104 0.009
Tags: @product
1:29.086
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.011
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.431
Then Tails is running from USB drive "old" 0.296
And all tps features are active 1.095
When I write some files expected to persist 1.376
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.068
And I take note of which tps features are available 0.169
And I shutdown Tails and wait for the computer to power off 8.116
# 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.922
After features/support/hooks.rb:335 0.320
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.906
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.695
And I log in to a new session 14.622
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.793
And I plug USB drive "to_upgrade" 2.250
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.212
Then the running Tails is installed on USB drive "to_upgrade" 15.054
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:335 3.964
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.599
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.707
Then all tps features from the old Tails version are active 0.932
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.525
And the expected persistent files created with the old Tails version are present in the filesystem 1.163
And all persistent directories from the old Tails version have safe access rights 1.974
After features/support/hooks.rb:335 0.691
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
3:43.986
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.689
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
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.423
When the network is plugged 0.016
And Tor is ready 13.373
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.090
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.100
Given I shutdown Tails and wait for the computer to power off 9.512
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.156
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.289
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.270
When the network is plugged 0.019
And Tor is ready 9.982
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.648
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.820
Given I shutdown Tails and wait for the computer to power off 8.227
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.656
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.132
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.016
And Tor is ready 10.214
Then the Upgrader considers the system as up-to-date 10.546
# 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.457
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.450
After features/support/hooks.rb:335 0.969
After features/support/hooks.rb:104 0.021
Tags: @product @automatic_upgrade
20.272
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.614
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.939
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.237
After features/support/hooks.rb:335 0.956
After features/support/hooks.rb:104 0.000