Project Number Date
test_Tails_ISO_stable 6738 12 Oct 2026, 12:32

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:5.459 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:12.763
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 16.423
When I start Tails from USB drive "old" with network unplugged 52.181
Then the boot device has safe access rights 2.361
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.154
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 3.875
After features/support/hooks.rb:108 0.007
Tags: @product
1:30.854
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 53.469
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 25.420
And I take note of which tps features are available 7.147
Then a Tails persistence partition exists on USB drive "old" 0.513
And I shutdown Tails and wait for the computer to power off 3.949
After features/support/hooks.rb:339 0.551
After features/support/hooks.rb:108 0.012
Tags: @product
1:42.223
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.116
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.121
Then Tails is running from USB drive "old" 0.228
And all tps features are active 8.027
When I write some files expected to persist 1.268
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.351
And all persistent directories from the old Tails version have safe access rights 2.140
And I take note of which tps features are available 7.889
And I shutdown Tails and wait for the computer to power off 4.363
# 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.516
After features/support/hooks.rb:339 0.127
After features/support/hooks.rb:108 0.007
Tags: @product
2:17.124
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.929
And I log in to a new session 12.344
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.790
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.303
Then the running Tails is installed on USB drive "to_upgrade" 20.250
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 3.624
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.097
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.063
Then all tps features from the old Tails version are active 1.089
And Tails is running from USB drive "to_upgrade" 0.188
And the boot device has safe access rights 2.054
And the expected persistent files created with the old Tails version are present in the filesystem 0.909
And all persistent directories from the old Tails version have safe access rights 1.700
After features/support/hooks.rb:339 0.621
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:47.279
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 9.046
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.027
And Tor is ready 12.596
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.123
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.762
Given I shutdown Tails and wait for the computer to power off 5.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.927
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 10.545
And the file system changes introduced in version 6.2~testoverlayfs are present 0.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.212
When the network is plugged 0.031
And Tor is ready 11.360
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.326
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.901
Given I shutdown Tails and wait for the computer to power off 4.430
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.984
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.780
And the file system changes introduced in version 6.3~testoverlayfs are present 0.334
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.164
When the network is plugged 0.036
And Tor is ready 10.040
Then the Upgrader considers the system as up-to-date 0.121
# 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.385
After features/support/hooks.rb:339 0.659
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
20.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.767
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 10.598
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.405
After features/support/hooks.rb:339 0.711
After features/support/hooks.rb:108 0.000