Project Number Date
test_Tails_ISO_21643-uefi-db 3 11 Jun 2026, 02:03

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:45.157 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:10.641
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.491
When I start Tails from USB drive "old" with network unplugged 52.203
Then the boot device has safe access rights 3.129
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:335 3.501
After features/support/hooks.rb:104 0.043
Tags: @product
1:29.366
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 54.716
Then Tails is running from USB drive "old" 0.282
And I create a persistent partition 24.954
And I take note of which tps features are available 0.350
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 8.447
After features/support/hooks.rb:335 0.579
After features/support/hooks.rb:104 0.007
Tags: @product
1:29.372
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.432
Then Tails is running from USB drive "old" 0.269
And all tps features are active 1.241
When I write some files expected to persist 1.239
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.342
And all persistent directories from the old Tails version have safe access rights 1.830
And I take note of which tps features are available 0.145
And I shutdown Tails and wait for the computer to power off 8.392
# 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.201
After features/support/hooks.rb:335 0.464
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.617
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.472
And I log in to a new session 13.554
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.845
And I plug USB drive "to_upgrade" 2.268
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.152
Then the running Tails is installed on USB drive "to_upgrade" 16.020
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:335 2.398
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.825
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.057
Then all tps features from the old Tails version are active 1.173
And Tails is running from USB drive "to_upgrade" 0.265
And the boot device has safe access rights 2.638
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.190
After features/support/hooks.rb:335 1.015
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:47.658
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.719
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.321
When the network is plugged 0.018
And Tor is ready 13.679
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.809
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.681
Given I shutdown Tails and wait for the computer to power off 9.756
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.378
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.264
And the file system changes introduced in version 6.2~testoverlayfs are present 0.261
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.178
# 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.205
When the network is plugged 0.023
And Tor is ready 12.033
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.088
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.707
Given I shutdown Tails and wait for the computer to power off 8.100
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.229
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.212
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.019
And Tor is ready 10.144
Then the Upgrader considers the system as up-to-date 10.555
# 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.472
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:335 0.817
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
21.675
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.289
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.759
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.137
After features/support/hooks.rb:335 0.530
After features/support/hooks.rb:104 0.000