Project Number Date
test_Tails_ISO_21643-uefi-db 1 09 Jun 2026, 14:32

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.468 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:14.680
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 14.136
When I start Tails from USB drive "old" with network unplugged 55.758
Then the boot device has safe access rights 2.919
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:335 1.461
After features/support/hooks.rb:104 0.008
Tags: @product
1:30.526
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 58.729
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 25.979
And I take note of which tps features are available 0.450
Then a Tails persistence partition exists on USB drive "old" 0.666
And I shutdown Tails and wait for the computer to power off 4.305
After features/support/hooks.rb:335 0.342
After features/support/hooks.rb:104 0.009
Tags: @product
1:30.375
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.326
Then Tails is running from USB drive "old" 0.227
And all tps features are active 1.290
When I write some files expected to persist 1.339
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.321
And all persistent directories from the old Tails version have safe access rights 2.107
And I take note of which tps features are available 0.164
And I shutdown Tails and wait for the computer to power off 7.070
# 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.256
After features/support/hooks.rb:335 0.452
After features/support/hooks.rb:104 0.009
Tags: @product
2:17.011
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 9.376
And I log in to a new session 14.283
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.918
And I plug USB drive "to_upgrade" 2.265
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.801
Then the running Tails is installed on USB drive "to_upgrade" 17.045
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:335 3.891
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.177
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.194
Then all tps features from the old Tails version are active 1.311
And Tails is running from USB drive "to_upgrade" 0.278
And the boot device has safe access rights 2.848
And the expected persistent files created with the old Tails version are present in the filesystem 1.242
And all persistent directories from the old Tails version have safe access rights 2.226
After features/support/hooks.rb:335 0.605
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:59.502
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 9.088
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.019
And Tor is ready 18.077
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.813
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.478
Given I shutdown Tails and wait for the computer to power off 9.796
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.597
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.226
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.220
When the network is plugged 0.021
And Tor is ready 11.595
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.863
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.456
Given I shutdown Tails and wait for the computer to power off 8.251
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.624
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.300
And the file system changes introduced in version 6.3~testoverlayfs are present 0.345
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.225
When the network is plugged 0.016
And Tor is ready 10.301
Then the Upgrader considers the system as up-to-date 10.629
# 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.343
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:335 0.964
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
22.194
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.884
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.228
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.728
After features/support/hooks.rb:335 1.194
After features/support/hooks.rb:104 0.000