Project Number Date
test_Tails_ISO_stable 6360 08 May 2026, 13:28

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:34.080 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.940
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.081
When I start Tails from USB drive "old" with network unplugged 53.873
Then the boot device has safe access rights 3.169
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.414
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 55.042
Then Tails is running from USB drive "old" 0.266
And I create a persistent partition 23.886
And I take note of which tps features are available 0.788
Then a Tails persistence partition exists on USB drive "old" 0.594
And I shutdown Tails and wait for the computer to power off 8.007
After features/support/hooks.rb:331 0.204
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.314
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.132
Then Tails is running from USB drive "old" 0.233
And all tps features are active 1.339
When I write some files expected to persist 1.453
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.577
And all persistent directories from the old Tails version have safe access rights 2.133
And I take note of which tps features are available 0.241
And I shutdown Tails and wait for the computer to power off 7.985
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.906
After features/support/hooks.rb:331 0.543
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.842
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.065
And I log in to a new session 13.524
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.870
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.579
Then the running Tails is installed on USB drive "to_upgrade" 16.243
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:331 2.302
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.108
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.997
Then all tps features from the old Tails version are active 1.022
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.882
And the expected persistent files created with the old Tails version are present in the filesystem 1.108
And all persistent directories from the old Tails version have safe access rights 1.825
After features/support/hooks.rb:331 0.497
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
4:32.100
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 8.303
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.318
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.013
And Tor is ready 19.419
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.605
Given I shutdown Tails and wait for the computer to power off 19.569
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.459
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.304
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.236
When the network is plugged 0.014
And Tor is ready 20.215
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.530
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.936
Given I shutdown Tails and wait for the computer to power off 17.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.340
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.257
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.017
And Tor is ready 20.047
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.293
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.460
After features/support/hooks.rb:331 0.821
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.992
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.492
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.106
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 18.751
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.351
After features/support/hooks.rb:331 0.764
After features/support/hooks.rb:100 0.000