Project Number Date
test_Tails_ISO_devel 4412 23 May 2026, 11:02

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:12.467 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.468
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.001
When I start Tails from USB drive "old" with network unplugged 57.154
Then the boot device has safe access rights 2.516
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:335 1.311
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.985
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 51.836
Then Tails is running from USB drive "old" 0.214
And I create a persistent partition 23.982
And I take note of which tps features are available 0.318
Then a Tails persistence partition exists on USB drive "old" 0.554
And I shutdown Tails and wait for the computer to power off 8.026
After features/support/hooks.rb:335 0.419
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.834
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.776
Then Tails is running from USB drive "old" 0.255
And all tps features are active 1.098
When I write some files expected to persist 1.273
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.140
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 1.921
And I take note of which tps features are available 0.140
And I shutdown Tails and wait for the computer to power off 7.935
# 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" 11.942
After features/support/hooks.rb:335 0.453
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.530
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.049
And I log in to a new session 12.382
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.685
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.328
Then the running Tails is installed on USB drive "to_upgrade" 14.546
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:335 3.814
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.818
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.287
Then all tps features from the old Tails version are active 0.984
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.370
And the expected persistent files created with the old Tails version are present in the filesystem 1.045
And all persistent directories from the old Tails version have safe access rights 1.856
After features/support/hooks.rb:335 0.864
After features/support/hooks.rb:104 0.019
3:31.493
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.887
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
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.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.017
And Tor is ready 12.913
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.401
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.278
Given I shutdown Tails and wait for the computer to power off 9.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.729
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.129
And the file system changes introduced in version 6.2~testoverlayfs are present 0.249
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.197
When the network is plugged 0.015
And Tor is ready 10.608
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.473
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.194
Given I shutdown Tails and wait for the computer to power off 4.139
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.456
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.117
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.209
When the network is plugged 0.017
And Tor is ready 11.072
Then the Upgrader considers the system as up-to-date 10.484
# 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.348
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.364
After features/support/hooks.rb:335 0.834
After features/support/hooks.rb:104 0.010
20.339
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.315
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.045
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 11.034
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.680
After features/support/hooks.rb:335 0.871
After features/support/hooks.rb:104 0.000