Project Number Date
test_Tails_ISO_21322-change-domain-deb.tails.boum.org 2 19 May 2026, 07:38

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:5.285 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:16.038
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 12.631
When I start Tails from USB drive "old" with network unplugged 58.951
Then the boot device has safe access rights 2.692
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.162
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:335 3.559
After features/support/hooks.rb:104 0.006
Tags: @product
1:21.289
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 "old" with network unplugged and I login 51.804
Then Tails is running from USB drive "old" 0.228
And I create a persistent partition 24.230
And I take note of which tps features are available 0.304
Then a Tails persistence partition exists on USB drive "old" 0.519
And I shutdown Tails and wait for the computer to power off 4.152
After features/support/hooks.rb:335 0.564
After features/support/hooks.rb:104 0.007
Tags: @product
1:22.794
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.013
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.066
Then Tails is running from USB drive "old" 0.268
And all tps features are active 1.274
When I write some files expected to persist 1.197
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.238
And all persistent directories from the old Tails version have safe access rights 1.755
And I take note of which tps features are available 0.141
And I shutdown Tails and wait for the computer to power off 7.858
# 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.769
After features/support/hooks.rb:335 0.496
After features/support/hooks.rb:104 0.006
Tags: @product
2:8.625
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 7.509
And I log in to a new session 11.794
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.667
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.098
Then the running Tails is installed on USB drive "to_upgrade" 15.047
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.161
After features/support/hooks.rb:335 2.069
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.113
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.380
Then all tps features from the old Tails version are active 0.916
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 2.417
And the expected persistent files created with the old Tails version are present in the filesystem 1.116
And all persistent directories from the old Tails version have safe access rights 1.874
After features/support/hooks.rb:335 0.607
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:30.582
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.942
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
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.195
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.312
When the network is plugged 0.057
And Tor is ready 12.911
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.316
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.423
Given I shutdown Tails and wait for the computer to power off 9.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.049
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.055
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.110
# 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.186
When the network is plugged 0.014
And Tor is ready 9.663
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.216
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.420
Given I shutdown Tails and wait for the computer to power off 4.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.073
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.088
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.017
And Tor is ready 10.703
Then the Upgrader considers the system as up-to-date 10.521
# 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.726
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.391
After features/support/hooks.rb:335 0.924
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
19.840
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.154
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 11.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.176
After features/support/hooks.rb:335 0.939
After features/support/hooks.rb:104 0.000