Project Number Date
test_Tails_ISO_stable 6460 18 Jun 2026, 07:34

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:39.785 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:2.554
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.147
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 13.075
When I start Tails from USB drive "old" with network unplugged 45.253
Then the boot device has safe access rights 2.420
And Tails is running from USB drive "old" 0.204
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.429
After features/support/hooks.rb:108 0.017
Tags: @product
1:29.270
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login 51.693
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 24.145
And I take note of which tps features are available 4.149
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 8.400
After features/support/hooks.rb:339 0.593
After features/support/hooks.rb:108 0.018
Tags: @product
1:34.508
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.124
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.067
Then Tails is running from USB drive "old" 0.212
And all tps features are active 4.738
When I write some files expected to persist 1.262
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.321
And all persistent directories from the old Tails version have safe access rights 1.968
And I take note of which tps features are available 4.005
And I shutdown Tails and wait for the computer to power off 6.810
# 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.826
After features/support/hooks.rb:339 0.331
After features/support/hooks.rb:108 0.018
Tags: @product
2:9.027
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.152
And I log in to a new session 11.473
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.766
And I plug USB drive "to_upgrade" 2.190
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.133
Then the running Tails is installed on USB drive "to_upgrade" 15.047
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 2.050
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.114
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.048
Then all tps features from the old Tails version are active 1.042
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 2.569
And the expected persistent files created with the old Tails version are present in the filesystem 1.078
And all persistent directories from the old Tails version have safe access rights 1.986
After features/support/hooks.rb:339 0.782
After features/support/hooks.rb:108 0.024
Tags: @product @automatic_upgrade
3:51.407
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.023
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.314
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.150
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.016
And Tor is ready 13.489
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.558
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.913
Given I shutdown Tails and wait for the computer to power off 9.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.614
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.843
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
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.185
# 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.211
When the network is plugged 0.014
And Tor is ready 9.669
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.351
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.816
Given I shutdown Tails and wait for the computer to power off 4.602
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.958
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.705
And the file system changes introduced in version 6.3~testoverlayfs are present 0.360
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.214
When the network is plugged 0.017
And Tor is ready 10.020
Then the Upgrader considers the system as up-to-date 10.513
# 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.409
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.422
After features/support/hooks.rb:339 1.127
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
20.900
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.620
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.086
And the signing key used by the Upgrader is outdated 0.144
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.103
After features/support/hooks.rb:339 0.854
After features/support/hooks.rb:108 0.000