Project Number Date
test_Tails_ISO_stable 6409 28 May 2026, 11:34

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 11:37.355 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:3.253
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.011
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.732
When I start Tails from USB drive "old" with network unplugged 44.952
Then the boot device has safe access rights 2.747
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:335 1.180
After features/support/hooks.rb:104 0.006
Tags: @product
1:31.052
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 55.357
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 26.262
And I take note of which tps features are available 0.345
Then a Tails persistence partition exists on USB drive "old" 0.613
And I shutdown Tails and wait for the computer to power off 8.136
After features/support/hooks.rb:335 0.368
After features/support/hooks.rb:104 0.007
Tags: @product
1:30.365
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.365
Then Tails is running from USB drive "old" 0.277
And all tps features are active 1.130
When I write some files expected to persist 1.268
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 1.958
And I take note of which tps features are available 0.194
And I shutdown Tails and wait for the computer to power off 8.423
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.162
After features/support/hooks.rb:335 0.467
After features/support/hooks.rb:104 0.006
Tags: @product
2:10.904
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.291
And I log in to a new session 12.638
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.827
And I plug USB drive "to_upgrade" 2.279
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.163
Then the running Tails is installed on USB drive "to_upgrade" 15.436
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:335 2.189
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.005
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.487
Then all tps features from the old Tails version are active 1.117
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.496
And the expected persistent files created with the old Tails version are present in the filesystem 1.209
And all persistent directories from the old Tails version have safe access rights 2.365
After features/support/hooks.rb:335 0.727
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:48.777
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.738
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.015
And Tor is ready 12.671
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.809
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.910
Given I shutdown Tails and wait for the computer to power off 9.945
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.509
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.341
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.264
When the network is plugged 0.016
And Tor is ready 10.700
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.572
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.588
Given I shutdown Tails and wait for the computer to power off 8.112
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.167
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.345
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.214
When the network is plugged 0.024
And Tor is ready 10.420
Then the Upgrader considers the system as up-to-date 10.575
# 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.317
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.374
After features/support/hooks.rb:335 0.666
After features/support/hooks.rb:104 0.025
Tags: @product @automatic_upgrade
20.997
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.391
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 10.543
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.691
After features/support/hooks.rb:335 0.744
After features/support/hooks.rb:104 0.000