Project Number Date
test_Tails_ISO_devel 4357 21 Apr 2026, 22:34

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:30.377 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:2.957
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.578
When I start Tails from USB drive "old" with network unplugged 44.719
Then the boot device has safe access rights 2.785
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 1.297
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.831
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 54.707
Then Tails is running from USB drive "old" 0.280
And I create a persistent partition 25.112
And I take note of which tps features are available 0.737
Then a Tails persistence partition exists on USB drive "old" 0.576
And I shutdown Tails and wait for the computer to power off 8.323
After features/support/hooks.rb:331 0.624
After features/support/hooks.rb:100 0.008
Tags: @product
1:30.690
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.476
Then Tails is running from USB drive "old" 0.402
And all tps features are active 1.468
When I write some files expected to persist 1.530
# 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.501
And all persistent directories from the old Tails version have safe access rights 1.956
And I take note of which tps features are available 0.167
And I shutdown Tails and wait for the computer to power off 8.089
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.807
After features/support/hooks.rb:331 0.155
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.206
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 8.108
And I log in to a new session 12.840
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.859
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.553
Then the running Tails is installed on USB drive "to_upgrade" 16.318
And I unplug USB drive "to_upgrade" 0.162
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:331 1.029
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.453
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.963
Then all tps features from the old Tails version are active 1.056
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 2.647
And the expected persistent files created with the old Tails version are present in the filesystem 1.265
And all persistent directories from the old Tails version have safe access rights 2.171
After features/support/hooks.rb:331 0.805
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:23.231
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.163
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.456
When the network is plugged 0.020
And Tor is ready 22.143
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.376
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.849
Given I shutdown Tails and wait for the computer to power off 11.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.251
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.179
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.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.311
When the network is plugged 0.015
And Tor is ready 20.294
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.412
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.634
Given I shutdown Tails and wait for the computer to power off 8.402
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.766
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.080
And the file system changes introduced in version 6.3~testoverlayfs are present 0.433
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.017
And Tor is ready 21.144
Then the Upgrader considers the system as up-to-date 0.108
# 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.474
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.577
After features/support/hooks.rb:331 0.824
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
38.006
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.425
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.047
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.016
And Tor is ready 16.805
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.428
After features/support/hooks.rb:331 0.759
After features/support/hooks.rb:100 0.000