Project Number Date
test_Tails_ISO_devel 4301 29 Mar 2026, 08:06

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:37.607 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:6.265
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.097
When I start Tails from USB drive "old" with network unplugged 48.731
Then the boot device has safe access rights 2.624
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:331 1.246
After features/support/hooks.rb:100 0.008
Tags: @product
1:24.875
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 52.229
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 23.100
And I take note of which tps features are available 0.727
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 7.910
After features/support/hooks.rb:331 0.455
After features/support/hooks.rb:100 0.007
Tags: @product
1:19.541
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.705
Then Tails is running from USB drive "old" 0.251
And all tps features are active 1.054
When I write some files expected to persist 1.079
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.428
And all persistent directories from the old Tails version have safe access rights 1.866
And I take note of which tps features are available 0.190
And I shutdown Tails and wait for the computer to power off 4.141
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.561
After features/support/hooks.rb:331 0.278
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.950
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 7.960
And I log in to a new session 11.878
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.693
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.997
Then the running Tails is installed on USB drive "to_upgrade" 16.887
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:331 2.257
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.228
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.452
Then all tps features from the old Tails version are active 0.904
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.434
And the expected persistent files created with the old Tails version are present in the filesystem 1.096
And all persistent directories from the old Tails version have safe access rights 2.032
After features/support/hooks.rb:331 0.481
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:53.906
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.356
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.023
And Tor is ready 19.396
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.376
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.569
Given I shutdown Tails and wait for the computer to power off 19.947
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.631
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.075
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
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.147
# 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.017
And Tor is ready 41.095
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.370
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.998
Given I shutdown Tails and wait for the computer to power off 17.255
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.027
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.180
And the file system changes introduced in version 6.3~testoverlayfs are present 0.418
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.015
And Tor is ready 21.238
Then the Upgrader considers the system as up-to-date 0.108
# 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.369
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.388
After features/support/hooks.rb:331 1.024
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
26.839
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.812
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 18.255
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.402
After features/support/hooks.rb:331 1.096
After features/support/hooks.rb:100 0.000