Project Number Date
test_Tails_ISO_stable 6200 13 Mar 2026, 07:18

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:4.989 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:34.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.827
When I start Tails from USB drive "old" with network unplugged 1:15.920
Then the boot device has safe access rights 2.710
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 3.487
After features/support/hooks.rb:100 0.011
Tags: @product
1:25.257
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 51.859
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 23.656
And I take note of which tps features are available 0.714
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 8.130
After features/support/hooks.rb:331 0.598
After features/support/hooks.rb:100 0.006
Tags: @product
1:20.805
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.476
Then Tails is running from USB drive "old" 0.209
And all tps features are active 0.996
When I write some files expected to persist 1.296
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.159
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 1.822
And I take note of which tps features are available 0.144
And I shutdown Tails and wait for the computer to power off 4.218
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.972
After features/support/hooks.rb:331 0.555
After features/support/hooks.rb:100 0.006
Tags: @product
2:29.470
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 without a persistent partition and stopped at Tails Greeter's login screen 8.585
And I log in to a new session 16.808
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.904
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.394
Then the running Tails is installed on USB drive "to_upgrade" 17.276
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 4.124
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.476
Then all tps features from the old Tails version are active 0.977
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.393
And the expected persistent files created with the old Tails version are present in the filesystem 1.030
And all persistent directories from the old Tails version have safe access rights 1.871
After features/support/hooks.rb:331 0.710
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:39.635
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.465
And no SquashFS delta is installed 0.256
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.372
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.022
And Tor is ready 23.081
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.351
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.041
Given I shutdown Tails and wait for the computer to power off 27.944
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.354
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 1.121
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
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.136
# 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.211
When the network is plugged 0.019
And Tor is ready 20.447
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.341
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.862
Given I shutdown Tails and wait for the computer to power off 13.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.022
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.069
And the file system changes introduced in version 6.3~testoverlayfs are present 0.339
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.018
And Tor is ready 22.261
Then the Upgrader considers the system as up-to-date 0.097
# 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 3.837
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.394
After features/support/hooks.rb:331 1.138
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
28.601
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.783
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 20.116
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.356
After features/support/hooks.rb:331 0.602
After features/support/hooks.rb:100 0.000