Project Number Date
test_Tails_ISO_stable 6394 21 May 2026, 07: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 11:30.451 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.514
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.014
Given a computer 0.115
And I create a 7200 MiB disk named "old" 0.016
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.919
When I start Tails from USB drive "old" with network unplugged 53.231
Then the boot device has safe access rights 2.531
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:335 1.093
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.900
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 53.278
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 25.006
And I take note of which tps features are available 0.328
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 8.438
After features/support/hooks.rb:335 0.495
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.607
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.321
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.223
When I write some files expected to persist 1.359
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 1.906
And I take note of which tps features are available 0.241
And I shutdown Tails and wait for the computer to power off 4.255
# 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.378
After features/support/hooks.rb:335 0.253
After features/support/hooks.rb:104 0.017
Tags: @product
2:11.467
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.010
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.075
And I log in to a new session 13.031
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.859
And I plug USB drive "to_upgrade" 2.231
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.316
Then the running Tails is installed on USB drive "to_upgrade" 15.680
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.065
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.275
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.387
Then all tps features from the old Tails version are active 1.038
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.438
And the expected persistent files created with the old Tails version are present in the filesystem 1.107
And all persistent directories from the old Tails version have safe access rights 2.031
After features/support/hooks.rb:335 0.940
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:42.722
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 8.122
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.018
And Tor is ready 11.809
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.101
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.720
Given I shutdown Tails and wait for the computer to power off 9.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.739
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.166
# 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.258
When the network is plugged 0.014
And Tor is ready 10.346
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.213
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.200
Given I shutdown Tails and wait for the computer to power off 8.572
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.650
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.323
And the file system changes introduced in version 6.3~testoverlayfs are present 0.419
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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.020
And Tor is ready 10.348
Then the Upgrader considers the system as up-to-date 10.576
# 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.122
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.369
After features/support/hooks.rb:335 0.755
After features/support/hooks.rb:104 0.017
Tags: @product @automatic_upgrade
20.964
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.584
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.847
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.148
After features/support/hooks.rb:335 0.797
After features/support/hooks.rb:104 0.000