Project Number Date
test_Tails_ISO_devel 4216 06 Feb 2026, 11:46

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:2.561 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:3.704
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.047
When I start Tails from USB drive "old" with network unplugged 44.909
Then the boot device has safe access rights 2.878
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:331 3.416
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.281
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 53.895
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 23.619
And I take note of which tps features are available 0.719
Then a Tails persistence partition exists on USB drive "old" 0.623
And I shutdown Tails and wait for the computer to power off 8.089
After features/support/hooks.rb:331 0.590
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.720
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.596
Then Tails is running from USB drive "old" 0.252
And all tps features are active 1.254
When I write some files expected to persist 1.497
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 2.100
And I take note of which tps features are available 0.227
And I shutdown Tails and wait for the computer to power off 8.358
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.758
After features/support/hooks.rb:331 0.104
After features/support/hooks.rb:100 0.007
Tags: @product
2:15.537
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 without a persistent partition and stopped at Tails Greeter's login screen 8.251
And I log in to a new session 13.130
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.872
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.135
Then the running Tails is installed on USB drive "to_upgrade" 16.661
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:331 3.857
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.470
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:13.190
Then all tps features from the old Tails version are active 1.052
And Tails is running from USB drive "to_upgrade" 0.230
And the boot device has safe access rights 2.701
And the expected persistent files created with the old Tails version are present in the filesystem 1.201
And all persistent directories from the old Tails version have safe access rights 2.040
After features/support/hooks.rb:331 0.868
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
4:4.612
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.420
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
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.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.408
When the network is plugged 0.018
And Tor is ready 13.528
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.758
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.151
Given I shutdown Tails and wait for the computer to power off 12.719
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.393
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.236
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.213
When the network is plugged 0.017
And Tor is ready 10.764
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.665
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.548
Given I shutdown Tails and wait for the computer to power off 8.028
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.167
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.286
And the file system changes introduced in version 6.3~testoverlayfs are present 0.362
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.014
And Tor is ready 10.982
Then the Upgrader considers the system as up-to-date 10.689
# 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.361
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.400
After features/support/hooks.rb:331 0.885
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
22.234
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 7.894
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.535
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.338
After features/support/hooks.rb:331 0.978
After features/support/hooks.rb:100 0.000