Project Number Date
test_Tails_ISO_release-process-7.7.3 5 11 May 2026, 19:14

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:17.648 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:26.377
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.530
When I start Tails from USB drive "old" with network unplugged 1:7.838
Then the boot device has safe access rights 3.077
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.761
After features/support/hooks.rb:100 0.032
Tags: @product
1:33.153
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 57.302
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 25.698
And I take note of which tps features are available 0.779
Then a Tails persistence partition exists on USB drive "old" 0.590
And I shutdown Tails and wait for the computer to power off 8.452
After features/support/hooks.rb:331 0.353
After features/support/hooks.rb:100 0.023
Tags: @product
1:29.959
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.479
Then Tails is running from USB drive "old" 0.250
And all tps features are active 1.139
When I write some files expected to persist 1.321
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.326
And I take note of which tps features are available 0.213
And I shutdown Tails and wait for the computer to power off 6.969
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.515
After features/support/hooks.rb:331 0.421
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.043
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 without a persistent partition and stopped at Tails Greeter's login screen 8.661
And I log in to a new session 13.356
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.079
And I plug USB drive "to_upgrade" 2.276
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.742
Then the running Tails is installed on USB drive "to_upgrade" 17.638
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 2.133
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.603
Then all tps features from the old Tails version are active 1.114
And Tails is running from USB drive "to_upgrade" 0.371
And the boot device has safe access rights 2.977
And the expected persistent files created with the old Tails version are present in the filesystem 1.387
And all persistent directories from the old Tails version have safe access rights 2.162
After features/support/hooks.rb:331 0.578
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:49.592
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.469
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.019
And Tor is ready 23.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.412
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.453
Given I shutdown Tails and wait for the computer to power off 20.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.272
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.263
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.230
When the network is plugged 0.026
And Tor is ready 20.653
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.404
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.069
Given I shutdown Tails and wait for the computer to power off 18.593
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.572
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.219
And the file system changes introduced in version 6.3~testoverlayfs are present 0.392
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.237
When the network is plugged 0.018
And Tor is ready 22.070
Then the Upgrader considers the system as up-to-date 0.118
# 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.225
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.643
After features/support/hooks.rb:331 0.929
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
27.808
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.948
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
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.048
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.057
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.423
After features/support/hooks.rb:331 0.958
After features/support/hooks.rb:100 0.000