Project Number Date
test_Tails_ISO_devel 4433 05 Jun 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 10:48.703 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
57.651
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.033
When I start Tails from USB drive "old" with network unplugged 40.234
Then the boot device has safe access rights 2.578
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:335 3.495
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.957
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 52.215
Then Tails is running from USB drive "old" 0.260
And I create a persistent partition 23.416
And I take note of which tps features are available 0.350
Then a Tails persistence partition exists on USB drive "old" 0.566
And I shutdown Tails and wait for the computer to power off 8.089
After features/support/hooks.rb:335 0.376
After features/support/hooks.rb:104 0.007
Tags: @product
1:22.893
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.236
Then Tails is running from USB drive "old" 0.212
And all tps features are active 1.085
When I write some files expected to persist 1.127
# 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.335
And all persistent directories from the old Tails version have safe access rights 1.907
And I take note of which tps features are available 0.189
And I shutdown Tails and wait for the computer to power off 7.844
# 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.737
After features/support/hooks.rb:335 0.469
After features/support/hooks.rb:104 0.008
Tags: @product
2:7.625
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 without a persistent partition and stopped at Tails Greeter's login screen 7.806
And I log in to a new session 11.019
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.831
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.141
Then the running Tails is installed on USB drive "to_upgrade" 14.337
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:335 1.956
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.793
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.295
Then all tps features from the old Tails version are active 0.930
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.328
And the expected persistent files created with the old Tails version are present in the filesystem 1.075
And all persistent directories from the old Tails version have safe access rights 1.857
After features/support/hooks.rb:335 0.942
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
3:30.308
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.253
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.015
And Tor is ready 13.300
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.553
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.242
Given I shutdown Tails and wait for the computer to power off 6.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.848
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.036
And the file system changes introduced in version 6.2~testoverlayfs are present 0.223
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.184
When the network is plugged 0.015
And Tor is ready 9.616
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.083
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.558
Given I shutdown Tails and wait for the computer to power off 8.089
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.959
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.117
And the file system changes introduced in version 6.3~testoverlayfs are present 0.421
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.017
And Tor is ready 9.610
Then the Upgrader considers the system as up-to-date 10.489
# 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.216
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:335 0.651
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.472
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.379
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.315
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.470
After features/support/hooks.rb:335 0.770
After features/support/hooks.rb:104 0.000