Project Number Date
test_Tails_ISO_stable 6472 26 Jun 2026, 11:45

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:28.236 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:19.160
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.861
When I start Tails from USB drive "old" with network unplugged 1:0.613
Then the boot device has safe access rights 2.830
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:339 1.544
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.070
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 56.823
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 25.581
And I take note of which tps features are available 4.511
Then a Tails persistence partition exists on USB drive "old" 0.625
And I shutdown Tails and wait for the computer to power off 8.227
After features/support/hooks.rb:339 0.339
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.219
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.066
Then Tails is running from USB drive "old" 0.278
And all tps features are active 5.554
When I write some files expected to persist 1.410
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.332
And all persistent directories from the old Tails version have safe access rights 2.111
And I take note of which tps features are available 4.242
And I shutdown Tails and wait for the computer to power off 8.693
# 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.281
After features/support/hooks.rb:339 0.145
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.505
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.437
And I log in to a new session 13.939
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.850
And I plug USB drive "to_upgrade" 2.319
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.488
Then the running Tails is installed on USB drive "to_upgrade" 16.151
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:339 2.015
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.059
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.348
Then all tps features from the old Tails version are active 1.210
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.623
And the expected persistent files created with the old Tails version are present in the filesystem 1.335
And all persistent directories from the old Tails version have safe access rights 2.213
After features/support/hooks.rb:339 0.654
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:2.393
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.463
And no SquashFS delta is installed 0.076
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.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.019
And Tor is ready 13.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.446
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.396
Given I shutdown Tails and wait for the computer to power off 9.706
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.215
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 6.318
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.417
When the network is plugged 0.015
And Tor is ready 10.029
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.372
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.683
Given I shutdown Tails and wait for the computer to power off 4.124
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.197
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.893
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.290
When the network is plugged 0.016
And Tor is ready 10.187
Then the Upgrader considers the system as up-to-date 10.624
# 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.743
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 1.103
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.828
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.257
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.596
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.649
After features/support/hooks.rb:339 0.930
After features/support/hooks.rb:108 0.000