Project Number Date
test_Tails_ISO_devel 4396 14 May 2026, 20:07

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:8.789 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:9.747
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 12.954
When I start Tails from USB drive "old" with network unplugged 52.803
Then the boot device has safe access rights 2.239
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:335 3.879
After features/support/hooks.rb:104 0.005
Tags: @product
1:23.218
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 53.347
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 24.313
And I take note of which tps features are available 0.335
Then a Tails persistence partition exists on USB drive "old" 0.565
And I shutdown Tails and wait for the computer to power off 4.376
After features/support/hooks.rb:335 0.651
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.727
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.636
Then Tails is running from USB drive "old" 0.243
And all tps features are active 1.060
When I write some files expected to persist 1.351
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.313
And all persistent directories from the old Tails version have safe access rights 1.778
And I take note of which tps features are available 0.143
And I shutdown Tails and wait for the computer to power off 7.884
# 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.046
After features/support/hooks.rb:335 0.575
After features/support/hooks.rb:104 0.008
Tags: @product
2:9.942
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.598
And I log in to a new session 12.886
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.705
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.034
Then the running Tails is installed on USB drive "to_upgrade" 15.235
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:335 3.699
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.510
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.560
Then all tps features from the old Tails version are active 1.019
And Tails is running from USB drive "to_upgrade" 0.268
And the boot device has safe access rights 2.584
And the expected persistent files created with the old Tails version are present in the filesystem 1.160
And all persistent directories from the old Tails version have safe access rights 1.833
After features/support/hooks.rb:335 0.714
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:33.398
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.940
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.583
When the network is plugged 0.022
And Tor is ready 12.955
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.299
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.648
Given I shutdown Tails and wait for the computer to power off 9.479
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.731
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.050
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.196
When the network is plugged 0.017
And Tor is ready 10.513
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.785
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.219
Given I shutdown Tails and wait for the computer to power off 7.947
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.368
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.169
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.174
When the network is plugged 0.015
And Tor is ready 10.508
Then the Upgrader considers the system as up-to-date 10.578
# 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.259
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.348
After features/support/hooks.rb:335 1.021
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.243
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.252
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 8.559
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.087
After features/support/hooks.rb:335 0.995
After features/support/hooks.rb:104 0.000