Project Number Date
test_Tails_ISO_stable 6379 15 May 2026, 11:35

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:58.079 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.747
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.197
When I start Tails from USB drive "old" with network unplugged 52.305
Then the boot device has safe access rights 3.392
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:335 1.462
After features/support/hooks.rb:104 0.007
Tags: @product
1:32.506
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.111
And I start Tails from USB drive "old" with network unplugged and I login 57.050
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 25.546
And I take note of which tps features are available 0.392
Then a Tails persistence partition exists on USB drive "old" 0.588
And I shutdown Tails and wait for the computer to power off 8.529
After features/support/hooks.rb:335 0.471
After features/support/hooks.rb:104 0.008
Tags: @product
1:32.574
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.002
Then Tails is running from USB drive "old" 0.309
And all tps features are active 1.312
When I write some files expected to persist 1.449
# 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.310
And all persistent directories from the old Tails version have safe access rights 2.007
And I take note of which tps features are available 0.177
And I shutdown Tails and wait for the computer to power off 7.954
# 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.776
After features/support/hooks.rb:335 0.262
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.813
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 without a persistent partition and stopped at Tails Greeter's login screen 7.621
And I log in to a new session 13.945
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.794
And I plug USB drive "to_upgrade" 2.260
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.380
Then the running Tails is installed on USB drive "to_upgrade" 16.486
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:335 2.102
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.498
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.010
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.040
Then all tps features from the old Tails version are active 0.980
And Tails is running from USB drive "to_upgrade" 0.254
And the boot device has safe access rights 2.744
And the expected persistent files created with the old Tails version are present in the filesystem 1.200
And all persistent directories from the old Tails version have safe access rights 2.162
After features/support/hooks.rb:335 0.764
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
3:51.592
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.680
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.357
When the network is plugged 0.016
And Tor is ready 14.449
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.934
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.701
Given I shutdown Tails and wait for the computer to power off 9.969
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.938
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.189
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.183
When the network is plugged 0.019
And Tor is ready 11.740
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.651
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.469
Given I shutdown Tails and wait for the computer to power off 4.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.105
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.325
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.165
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.325
When the network is plugged 0.024
And Tor is ready 10.128
Then the Upgrader considers the system as up-to-date 10.564
# 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.425
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:335 0.869
After features/support/hooks.rb:104 0.015
Tags: @product @automatic_upgrade
22.346
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 7.842
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 9.991
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.946
After features/support/hooks.rb:335 0.863
After features/support/hooks.rb:104 0.000