Project Number Date
test_Tails_ISO_stable 6514 21 Jul 2026, 07: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:9.169 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:6.860
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.467
When I start Tails from USB drive "old" with network unplugged 48.990
Then the boot device has safe access rights 2.651
And Tails is running from USB drive "old" 0.270
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 3.733
After features/support/hooks.rb:108 0.007
Tags: @product
1:34.056
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 54.989
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 25.719
And I take note of which tps features are available 4.319
Then a Tails persistence partition exists on USB drive "old" 0.688
And I shutdown Tails and wait for the computer to power off 8.017
After features/support/hooks.rb:339 0.339
After features/support/hooks.rb:108 0.007
Tags: @product
1:41.280
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.750
Then Tails is running from USB drive "old" 0.281
And all tps features are active 5.183
When I write some files expected to persist 1.386
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 1.870
And I take note of which tps features are available 3.769
And I shutdown Tails and wait for the computer to power off 8.358
# 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.120
After features/support/hooks.rb:339 0.544
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.754
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 7.516
And I log in to a new session 12.311
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.693
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.190
Then the running Tails is installed on USB drive "to_upgrade" 15.523
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 2.167
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.979
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.351
Then all tps features from the old Tails version are active 1.387
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.630
And the expected persistent files created with the old Tails version are present in the filesystem 1.098
And all persistent directories from the old Tails version have safe access rights 2.200
After features/support/hooks.rb:339 0.802
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:56.259
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.074
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
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.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.019
And Tor is ready 13.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.139
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.356
Given I shutdown Tails and wait for the computer to power off 6.982
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.304
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 6.119
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.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.175
# 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.232
When the network is plugged 0.026
And Tor is ready 10.972
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.558
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.382
Given I shutdown Tails and wait for the computer to power off 4.165
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.814
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.838
And the file system changes introduced in version 6.3~testoverlayfs are present 0.378
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.013
And Tor is ready 10.251
Then the Upgrader considers the system as up-to-date 10.636
# 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.334
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:339 0.679
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
21.978
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.662
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
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.041
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 11.988
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.003
After features/support/hooks.rb:339 0.814
After features/support/hooks.rb:108 0.000