Project Number Date
test_Tails_ISO_devel 4376 05 May 2026, 11:10

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 13:2.082 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.809
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.090
When I start Tails from USB drive "old" with network unplugged 51.576
Then the boot device has safe access rights 3.309
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.838
After features/support/hooks.rb:100 0.013
Tags: @product
1:32.713
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 59.304
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 24.659
And I take note of which tps features are available 0.843
Then a Tails persistence partition exists on USB drive "old" 0.586
And I shutdown Tails and wait for the computer to power off 7.027
After features/support/hooks.rb:331 0.174
After features/support/hooks.rb:100 0.010
Tags: @product
1:31.093
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.968
Then Tails is running from USB drive "old" 0.280
And all tps features are active 1.137
When I write some files expected to persist 1.386
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.495
And all persistent directories from the old Tails version have safe access rights 2.071
And I take note of which tps features are available 0.162
And I shutdown Tails and wait for the computer to power off 7.133
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.208
After features/support/hooks.rb:331 0.221
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.874
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.412
And I log in to a new session 14.316
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.965
And I plug USB drive "to_upgrade" 2.313
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.482
Then the running Tails is installed on USB drive "to_upgrade" 18.101
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:331 2.572
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.164
Then all tps features from the old Tails version are active 1.042
And Tails is running from USB drive "to_upgrade" 0.226
And the boot device has safe access rights 2.465
And the expected persistent files created with the old Tails version are present in the filesystem 1.175
And all persistent directories from the old Tails version have safe access rights 2.237
After features/support/hooks.rb:331 0.919
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:43.717
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.844
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.019
And Tor is ready 21.983
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.420
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.339
Given I shutdown Tails and wait for the computer to power off 19.159
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.321
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.361
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.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.222
When the network is plugged 0.014
And Tor is ready 21.166
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.408
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.522
Given I shutdown Tails and wait for the computer to power off 17.639
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.223
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.113
And the file system changes introduced in version 6.3~testoverlayfs are present 0.422
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.013
And Tor is ready 20.913
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 4.864
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.675
After features/support/hooks.rb:331 1.028
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
29.504
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.182
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.359
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.060
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 20.432
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.398
After features/support/hooks.rb:331 0.744
After features/support/hooks.rb:100 0.000