Project Number Date
test_Tails_ISO_stable 6436 09 Jun 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:1.373 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
59.781
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 12.904
When I start Tails from USB drive "old" with network unplugged 42.562
Then the boot device has safe access rights 2.576
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:335 3.876
After features/support/hooks.rb:104 0.006
Tags: @product
1:26.136
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 52.413
Then Tails is running from USB drive "old" 0.200
And I create a persistent partition 24.471
And I take note of which tps features are available 0.341
Then a Tails persistence partition exists on USB drive "old" 0.494
And I shutdown Tails and wait for the computer to power off 8.159
After features/support/hooks.rb:335 0.234
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.103
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.686
Then Tails is running from USB drive "old" 0.284
And all tps features are active 1.133
When I write some files expected to persist 1.172
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.309
And all persistent directories from the old Tails version have safe access rights 1.731
And I take note of which tps features are available 0.159
And I shutdown Tails and wait for the computer to power off 7.953
# 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" 11.449
After features/support/hooks.rb:335 0.257
After features/support/hooks.rb:104 0.007
Tags: @product
2:8.718
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.006
And I log in to a new session 11.602
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.768
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.213
Then the running Tails is installed on USB drive "to_upgrade" 14.672
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:335 2.043
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.737
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.979
Then all tps features from the old Tails version are active 1.153
And Tails is running from USB drive "to_upgrade" 0.231
And the boot device has safe access rights 2.445
And the expected persistent files created with the old Tails version are present in the filesystem 1.058
And all persistent directories from the old Tails version have safe access rights 1.816
After features/support/hooks.rb:335 0.972
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:34.046
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 8.022
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.024
And Tor is ready 11.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.707
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.823
Given I shutdown Tails and wait for the computer to power off 9.278
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.685
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.070
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.170
When the network is plugged 0.017
And Tor is ready 10.286
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.254
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.221
Given I shutdown Tails and wait for the computer to power off 7.969
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.172
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.179
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.018
And Tor is ready 10.892
Then the Upgrader considers the system as up-to-date 10.460
# 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.236
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.401
After features/support/hooks.rb:335 0.879
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.848
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.273
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.037
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.173
After features/support/hooks.rb:335 0.931
After features/support/hooks.rb:104 0.000