Project Number Date
test_Tails_ISO_stable 6122 05 Feb 2026, 13:39

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:11.830 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:15.872
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.654
When I start Tails from USB drive "old" with network unplugged 55.809
Then the boot device has safe access rights 3.523
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.654
After features/support/hooks.rb:100 0.024
Tags: @product
1:36.466
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 1:0.472
Then Tails is running from USB drive "old" 0.315
And I create a persistent partition 25.912
And I take note of which tps features are available 0.685
Then a Tails persistence partition exists on USB drive "old" 0.597
And I shutdown Tails and wait for the computer to power off 8.429
After features/support/hooks.rb:331 0.409
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.469
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.821
Then Tails is running from USB drive "old" 0.211
And all tps features are active 1.107
When I write some files expected to persist 1.266
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.310
And all persistent directories from the old Tails version have safe access rights 2.035
And I take note of which tps features are available 0.232
And I shutdown Tails and wait for the computer to power off 8.632
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.545
After features/support/hooks.rb:331 0.373
After features/support/hooks.rb:100 0.006
Tags: @product
2:15.273
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 9.325
And I log in to a new session 10.378
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.910
And I plug USB drive "to_upgrade" 2.613
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.258
Then the running Tails is installed on USB drive "to_upgrade" 17.491
And I unplug USB drive "to_upgrade" 0.148
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:331 2.300
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.024
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.874
Then all tps features from the old Tails version are active 1.216
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 2.881
And the expected persistent files created with the old Tails version are present in the filesystem 1.414
And all persistent directories from the old Tails version have safe access rights 2.212
After features/support/hooks.rb:331 0.749
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
3:53.357
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.121
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.023
And Tor is ready 13.910
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.997
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.022
Given I shutdown Tails and wait for the computer to power off 9.913
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.678
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.596
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# 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.371
When the network is plugged 0.027
And Tor is ready 10.497
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.981
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.197
Given I shutdown Tails and wait for the computer to power off 8.629
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.659
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.335
And the file system changes introduced in version 6.3~testoverlayfs are present 0.471
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.214
When the network is plugged 0.020
And Tor is ready 10.415
Then the Upgrader considers the system as up-to-date 10.632
# 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.253
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.545
After features/support/hooks.rb:331 1.228
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
21.367
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.421
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.134
After features/support/hooks.rb:331 0.976
After features/support/hooks.rb:100 0.000