Project Number Date
test_Tails_ISO_stable 6220 21 Mar 2026, 11:05

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:39.250 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:17.536
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.665
When I start Tails from USB drive "old" with network unplugged 59.104
Then the boot device has safe access rights 2.943
And Tails is running from USB drive "old" 0.287
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 1.482
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.812
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 55.256
Then Tails is running from USB drive "old" 0.289
And I create a persistent partition 24.043
And I take note of which tps features are available 0.711
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 7.958
After features/support/hooks.rb:331 0.543
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.733
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.461
Then Tails is running from USB drive "old" 0.308
And all tps features are active 1.211
When I write some files expected to persist 1.183
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 2.072
And I take note of which tps features are available 0.201
And I shutdown Tails and wait for the computer to power off 7.949
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.630
After features/support/hooks.rb:331 0.097
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.243
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 8.295
And I log in to a new session 13.027
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.848
And I plug USB drive "to_upgrade" 2.267
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.476
Then the running Tails is installed on USB drive "to_upgrade" 16.042
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:331 2.170
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.977
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.115
Then all tps features from the old Tails version are active 1.088
And Tails is running from USB drive "to_upgrade" 0.262
And the boot device has safe access rights 2.431
And the expected persistent files created with the old Tails version are present in the filesystem 1.082
And all persistent directories from the old Tails version have safe access rights 1.928
After features/support/hooks.rb:331 0.726
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:34.437
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.211
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
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.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.021
And Tor is ready 21.443
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.407
Given I shutdown Tails and wait for the computer to power off 14.653
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.759
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.305
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# 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.212
When the network is plugged 0.019
And Tor is ready 21.791
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.371
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.707
Given I shutdown Tails and wait for the computer to power off 17.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.730
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.269
And the file system changes introduced in version 6.3~testoverlayfs are present 0.362
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.016
And Tor is ready 20.686
Then the Upgrader considers the system as up-to-date 0.098
# 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 5.339
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.421
After features/support/hooks.rb:331 0.973
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
25.509
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 7.452
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 17.353
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.382
After features/support/hooks.rb:331 0.686
After features/support/hooks.rb:100 0.000