Project Number Date
test_Tails_ISO_devel 4422 30 May 2026, 11:09

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:2.853 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.112
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.887
When I start Tails from USB drive "old" with network unplugged 52.946
Then the boot device has safe access rights 2.506
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:335 1.281
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.621
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 52.757
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 23.892
And I take note of which tps features are available 0.304
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 7.861
After features/support/hooks.rb:335 0.228
After features/support/hooks.rb:104 0.006
Tags: @product
1:21.326
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 1:0.013
Then Tails is running from USB drive "old" 0.269
And all tps features are active 1.097
When I write some files expected to persist 1.503
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.281
And all persistent directories from the old Tails version have safe access rights 1.938
And I take note of which tps features are available 0.145
And I shutdown Tails and wait for the computer to power off 4.127
# 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.720
After features/support/hooks.rb:335 0.499
After features/support/hooks.rb:104 0.006
Tags: @product
2:8.914
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.940
And I log in to a new session 12.100
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.696
And I plug USB drive "to_upgrade" 2.276
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.907
Then the running Tails is installed on USB drive "to_upgrade" 14.734
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:335 1.931
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.422
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.932
Then all tps features from the old Tails version are active 0.915
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.297
And the expected persistent files created with the old Tails version are present in the filesystem 1.128
And all persistent directories from the old Tails version have safe access rights 1.862
After features/support/hooks.rb:335 0.831
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:30.865
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.249
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
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.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.019
And Tor is ready 11.956
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.468
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.875
Given I shutdown Tails and wait for the computer to power off 9.380
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.918
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 1.177
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.198
When the network is plugged 0.020
And Tor is ready 9.715
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.011
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.845
Given I shutdown Tails and wait for the computer to power off 4.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.971
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.137
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.117
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.664
Then the Upgrader considers the system as up-to-date 10.597
# 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.126
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.377
After features/support/hooks.rb:335 0.993
After features/support/hooks.rb:104 0.030
Tags: @product @automatic_upgrade
20.589
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.153
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.869
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.194
After features/support/hooks.rb:335 0.616
After features/support/hooks.rb:104 0.000