Project Number Date
test_Tails_ISO_stable 6477 30 Jun 2026, 11:40

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:31.147 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
58.948
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 12.779
When I start Tails from USB drive "old" with network unplugged 42.146
Then the boot device has safe access rights 2.206
And Tails is running from USB drive "old" 0.281
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:339 1.446
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.197
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 51.959
Then Tails is running from USB drive "old" 0.215
And I create a persistent partition 24.329
And I take note of which tps features are available 4.076
Then a Tails persistence partition exists on USB drive "old" 0.537
And I shutdown Tails and wait for the computer to power off 8.030
After features/support/hooks.rb:339 0.206
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.949
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.108
Then Tails is running from USB drive "old" 0.210
And all tps features are active 4.650
When I write some files expected to persist 1.293
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.288
And all persistent directories from the old Tails version have safe access rights 1.973
And I take note of which tps features are available 3.660
And I shutdown Tails and wait for the computer to power off 7.875
# 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.657
After features/support/hooks.rb:339 0.405
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.211
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.919
And I log in to a new session 12.445
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.698
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.206
Then the running Tails is installed on USB drive "to_upgrade" 14.482
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 0.674
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.588
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.856
Then all tps features from the old Tails version are active 0.957
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 2.513
And the expected persistent files created with the old Tails version are present in the filesystem 1.061
And all persistent directories from the old Tails version have safe access rights 1.844
After features/support/hooks.rb:339 0.649
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:51.455
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.914
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.357
When the network is plugged 0.016
And Tor is ready 12.902
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.948
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.481
Given I shutdown Tails and wait for the computer to power off 10.821
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.445
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.524
And the file system changes introduced in version 6.2~testoverlayfs are present 0.246
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.272
When the network is plugged 0.014
And Tor is ready 10.884
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.955
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.777
Given I shutdown Tails and wait for the computer to power off 7.935
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.746
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.527
And the file system changes introduced in version 6.3~testoverlayfs are present 0.350
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.020
And Tor is ready 11.412
Then the Upgrader considers the system as up-to-date 10.511
# 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.739
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.416
After features/support/hooks.rb:339 0.976
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.796
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.283
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.286
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.865
After features/support/hooks.rb:339 0.959
After features/support/hooks.rb:108 0.000