Project Number Date
test_Tails_ISO_stable 6468 22 Jun 2026, 11:46

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:41.577 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:6.069
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.049
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.765
When I start Tails from USB drive "old" with network unplugged 48.071
Then the boot device has safe access rights 2.501
And Tails is running from USB drive "old" 0.198
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:339 1.375
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.447
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 53.068
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 24.482
And I take note of which tps features are available 4.190
Then a Tails persistence partition exists on USB drive "old" 0.530
And I shutdown Tails and wait for the computer to power off 7.865
After features/support/hooks.rb:339 0.400
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.917
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.072
Then Tails is running from USB drive "old" 0.210
And all tps features are active 4.883
When I write some files expected to persist 1.280
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.005
And I take note of which tps features are available 3.761
And I shutdown Tails and wait for the computer to power off 4.201
# 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.868
After features/support/hooks.rb:339 0.375
After features/support/hooks.rb:108 0.007
Tags: @product
2:9.270
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.106
And I log in to a new session 11.815
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.888
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.122
Then the running Tails is installed on USB drive "to_upgrade" 14.844
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 2.806
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.035
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.913
Then all tps features from the old Tails version are active 1.078
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 2.574
And the expected persistent files created with the old Tails version are present in the filesystem 1.168
And all persistent directories from the old Tails version have safe access rights 1.914
After features/support/hooks.rb:339 0.688
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:51.280
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.973
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.018
And Tor is ready 13.462
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.315
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.141
Given I shutdown Tails and wait for the computer to power off 10.861
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.778
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.970
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.182
When the network is plugged 0.017
And Tor is ready 10.015
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.832
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.850
Given I shutdown Tails and wait for the computer to power off 8.090
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.524
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.592
And the file system changes introduced in version 6.3~testoverlayfs are present 0.317
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.015
And Tor is ready 10.391
Then the Upgrader considers the system as up-to-date 10.574
# 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.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.384
After features/support/hooks.rb:339 0.677
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
21.555
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.660
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.352
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.186
After features/support/hooks.rb:339 0.705
After features/support/hooks.rb:108 0.000