Project Number Date
test_Tails_ISO_add-team-sprint-template 2 21 May 2026, 17:26

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 12:3.415 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:25.875
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 14.015
When I start Tails from USB drive "old" with network unplugged 1:6.774
Then the boot device has safe access rights 3.135
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:335 3.969
After features/support/hooks.rb:104 0.006
Tags: @product
1:26.501
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 56.133
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 24.901
And I take note of which tps features are available 0.355
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 4.253
After features/support/hooks.rb:335 0.363
After features/support/hooks.rb:104 0.006
Tags: @product
1:31.380
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 with persistence enabled 1:4.736
Then Tails is running from USB drive "old" 0.246
And all tps features are active 1.383
When I write some files expected to persist 1.590
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 2.521
And I take note of which tps features are available 0.169
And I shutdown Tails and wait for the computer to power off 6.736
# 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" 13.256
After features/support/hooks.rb:335 0.447
After features/support/hooks.rb:104 0.007
Tags: @product
2:15.572
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 8.794
And I log in to a new session 15.017
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.860
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.117
Then the running Tails is installed on USB drive "to_upgrade" 16.233
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:335 2.437
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.796
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:5.369
Then all tps features from the old Tails version are active 1.020
And Tails is running from USB drive "to_upgrade" 0.270
And the boot device has safe access rights 2.678
And the expected persistent files created with the old Tails version are present in the filesystem 1.198
And all persistent directories from the old Tails version have safe access rights 2.202
After features/support/hooks.rb:335 1.128
After features/support/hooks.rb:104 0.035
Tags: @product @automatic_upgrade
3:49.799
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 with a persistent partition enabled and logged in 8.768
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.325
When the network is plugged 0.017
And Tor is ready 13.872
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.035
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.150
Given I shutdown Tails and wait for the computer to power off 9.592
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.180
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.316
And the file system changes introduced in version 6.2~testoverlayfs are present 0.276
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.187
# 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.230
When the network is plugged 0.013
And Tor is ready 10.002
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.119
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.670
Given I shutdown Tails and wait for the computer to power off 8.369
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.633
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.413
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.017
And Tor is ready 9.957
Then the Upgrader considers the system as up-to-date 10.660
# 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.850
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.435
After features/support/hooks.rb:335 0.816
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
21.489
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 7.605
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
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.018
And Tor is ready 10.808
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.737
After features/support/hooks.rb:335 0.735
After features/support/hooks.rb:104 0.000