Project Number Date
test_Tails_ISO_stable 6314 21 Apr 2026, 11:41

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 13:34.640 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:4.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.352
When I start Tails from USB drive "old" with network unplugged 46.165
Then the boot device has safe access rights 2.616
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.180
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 3.680
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.949
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 55.074
Then Tails is running from USB drive "old" 0.224
And I create a persistent partition 25.637
And I take note of which tps features are available 0.641
Then a Tails persistence partition exists on USB drive "old" 0.557
And I shutdown Tails and wait for the computer to power off 6.752
After features/support/hooks.rb:331 0.481
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.609
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.069
Then Tails is running from USB drive "old" 0.297
And all tps features are active 1.191
When I write some files expected to persist 1.250
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 1.841
And I take note of which tps features are available 0.155
And I shutdown Tails and wait for the computer to power off 8.142
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.994
After features/support/hooks.rb:331 0.231
After features/support/hooks.rb:100 0.008
Tags: @product
2:21.493
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.478
And I log in to a new session 19.273
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.772
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.860
Then the running Tails is installed on USB drive "to_upgrade" 16.553
And I unplug USB drive "to_upgrade" 0.169
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 3.761
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.756
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.471
Then all tps features from the old Tails version are active 1.190
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.700
And the expected persistent files created with the old Tails version are present in the filesystem 1.159
And all persistent directories from the old Tails version have safe access rights 1.904
After features/support/hooks.rb:331 1.005
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
5:6.905
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.838
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.291
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.020
And Tor is ready 44.131
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.364
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.277
Given I shutdown Tails and wait for the computer to power off 16.928
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.370
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.088
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.191
When the network is plugged 0.014
And Tor is ready 22.759
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.392
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.585
Given I shutdown Tails and wait for the computer to power off 17.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.077
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.162
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.062
And Tor is ready 22.723
Then the Upgrader considers the system as up-to-date 0.107
# 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.677
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.404
After features/support/hooks.rb:331 0.705
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
50.013
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.513
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 41.754
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.382
After features/support/hooks.rb:331 0.795
After features/support/hooks.rb:100 0.000