Project Number Date
test_Tails_ISO_stable 6385 19 May 2026, 14:01

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:59.039 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:7.111
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.070
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.215
When I start Tails from USB drive "old" with network unplugged 47.287
Then the boot device has safe access rights 3.690
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:335 1.399
After features/support/hooks.rb:104 0.007
Tags: @product
1:31.805
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 57.379
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 24.590
And I take note of which tps features are available 0.354
Then a Tails persistence partition exists on USB drive "old" 0.628
And I shutdown Tails and wait for the computer to power off 8.456
After features/support/hooks.rb:335 0.625
After features/support/hooks.rb:104 0.024
Tags: @product
1:33.869
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.010
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.834
Then Tails is running from USB drive "old" 0.323
And all tps features are active 1.307
When I write some files expected to persist 1.355
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.341
And all persistent directories from the old Tails version have safe access rights 1.837
And I take note of which tps features are available 0.176
And I shutdown Tails and wait for the computer to power off 8.035
# 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" 13.387
After features/support/hooks.rb:335 0.505
After features/support/hooks.rb:104 0.006
Tags: @product
2:15.948
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 without a persistent partition and stopped at Tails Greeter's login screen 8.684
And I log in to a new session 13.919
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.941
And I plug USB drive "to_upgrade" 2.283
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.216
Then the running Tails is installed on USB drive "to_upgrade" 17.624
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:335 2.020
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.607
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.200
Then all tps features from the old Tails version are active 1.425
And Tails is running from USB drive "to_upgrade" 0.267
And the boot device has safe access rights 3.221
And the expected persistent files created with the old Tails version are present in the filesystem 1.226
And all persistent directories from the old Tails version have safe access rights 2.196
After features/support/hooks.rb:335 0.793
After features/support/hooks.rb:104 0.037
Tags: @product @automatic_upgrade
3:53.658
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.552
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.407
When the network is plugged 0.019
And Tor is ready 12.619
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.322
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.129
Given I shutdown Tails and wait for the computer to power off 7.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.510
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.222
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.187
When the network is plugged 0.016
And Tor is ready 11.470
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.421
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.797
Given I shutdown Tails and wait for the computer to power off 7.228
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.656
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.267
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.220
When the network is plugged 0.014
And Tor is ready 12.160
Then the Upgrader considers the system as up-to-date 10.682
# 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.161
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.550
After features/support/hooks.rb:335 0.906
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
21.039
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 8.026
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
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.014
And Tor is ready 10.193
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.424
After features/support/hooks.rb:335 0.722
After features/support/hooks.rb:104 0.000