Project Number Date
test_Tails_ISO_devel 4401 18 May 2026, 11:06

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:42.765 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:13.477
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.310
When I start Tails from USB drive "old" with network unplugged 55.668
Then the boot device has safe access rights 2.666
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:335 1.367
After features/support/hooks.rb:104 0.007
Tags: @product
1:31.602
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 55.104
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 26.639
And I take note of which tps features are available 0.515
Then a Tails persistence partition exists on USB drive "old" 0.702
And I shutdown Tails and wait for the computer to power off 8.316
After features/support/hooks.rb:335 0.262
After features/support/hooks.rb:104 0.007
Tags: @product
1:29.894
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.258
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.238
When I write some files expected to persist 1.275
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.334
And all persistent directories from the old Tails version have safe access rights 1.881
And I take note of which tps features are available 0.207
And I shutdown Tails and wait for the computer to power off 8.060
# 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.056
After features/support/hooks.rb:335 0.535
After features/support/hooks.rb:104 0.015
Tags: @product
2:11.470
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 without a persistent partition and stopped at Tails Greeter's login screen 8.233
And I log in to a new session 12.385
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.881
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.809
Then the running Tails is installed on USB drive "to_upgrade" 15.665
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:335 2.164
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.509
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.028
Then all tps features from the old Tails version are active 1.064
And Tails is running from USB drive "to_upgrade" 0.264
And the boot device has safe access rights 2.721
And the expected persistent files created with the old Tails version are present in the filesystem 1.313
And all persistent directories from the old Tails version have safe access rights 2.065
After features/support/hooks.rb:335 0.741
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:45.879
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.426
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.338
When the network is plugged 0.052
And Tor is ready 12.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.665
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.907
Given I shutdown Tails and wait for the computer to power off 7.158
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.017
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.431
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.202
When the network is plugged 0.017
And Tor is ready 11.932
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.841
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.606
Given I shutdown Tails and wait for the computer to power off 7.979
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.952
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.385
And the file system changes introduced in version 6.3~testoverlayfs are present 0.394
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.015
And Tor is ready 10.897
Then the Upgrader considers the system as up-to-date 10.548
# 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.328
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:335 0.998
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
19.931
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.569
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
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.096
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.998
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.915
After features/support/hooks.rb:335 0.803
After features/support/hooks.rb:104 0.000