Project Number Date
test_Tails_ISO_stable 6469 23 Jun 2026, 11:29

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:30.689 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:7.018
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.044
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.035
When I start Tails from USB drive "old" with network unplugged 49.778
Then the boot device has safe access rights 2.399
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:339 3.582
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.546
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 51.303
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 23.470
And I take note of which tps features are available 4.043
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 7.843
After features/support/hooks.rb:339 0.300
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.837
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.895
Then Tails is running from USB drive "old" 0.210
And all tps features are active 4.829
When I write some files expected to persist 1.315
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.291
And all persistent directories from the old Tails version have safe access rights 1.882
And I take note of which tps features are available 3.690
And I shutdown Tails and wait for the computer to power off 7.812
# 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.713
After features/support/hooks.rb:339 0.526
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.961
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.054
And I log in to a new session 12.063
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.719
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.257
Then the running Tails is installed on USB drive "to_upgrade" 14.316
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:339 2.053
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.385
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.929
Then all tps features from the old Tails version are active 0.895
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.413
And the expected persistent files created with the old Tails version are present in the filesystem 1.048
And all persistent directories from the old Tails version have safe access rights 1.739
After features/support/hooks.rb:339 0.860
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:43.247
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.968
And no SquashFS delta is installed 0.051
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.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.221
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.015
And Tor is ready 12.548
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.736
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.408
Given I shutdown Tails and wait for the computer to power off 9.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.107
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.023
And the file system changes introduced in version 6.2~testoverlayfs are present 0.354
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.213
When the network is plugged 0.019
And Tor is ready 10.667
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.302
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.162
Given I shutdown Tails and wait for the computer to power off 4.006
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.490
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.804
And the file system changes introduced in version 6.3~testoverlayfs are present 0.347
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.020
And Tor is ready 10.626
Then the Upgrader considers the system as up-to-date 10.482
# 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 3.769
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.670
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.693
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.297
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 9.065
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.977
After features/support/hooks.rb:339 1.039
After features/support/hooks.rb:108 0.000