Project Number Date
test_Tails_ISO_devel 4449 16 Jun 2026, 11:29

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:37.839 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:15.941
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 14.095
When I start Tails from USB drive "old" with network unplugged 57.348
Then the boot device has safe access rights 2.541
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.477
After features/support/hooks.rb:108 0.022
Tags: @product
1:38.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.191
And I start Tails from USB drive "old" with network unplugged and I login 58.065
Then Tails is running from USB drive "old" 0.260
And I create a persistent partition 27.091
And I take note of which tps features are available 5.292
Then a Tails persistence partition exists on USB drive "old" 0.517
And I shutdown Tails and wait for the computer to power off 7.060
After features/support/hooks.rb:339 0.409
After features/support/hooks.rb:108 0.025
Tags: @product
1:43.362
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.251
Then Tails is running from USB drive "old" 0.247
And all tps features are active 5.773
When I write some files expected to persist 1.283
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 1.821
And I take note of which tps features are available 4.157
And I shutdown Tails and wait for the computer to power off 7.434
# 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.757
After features/support/hooks.rb:339 0.528
After features/support/hooks.rb:108 0.023
Tags: @product
2:14.199
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.504
And I log in to a new session 13.770
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.956
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.454
Then the running Tails is installed on USB drive "to_upgrade" 15.973
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.750
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.514
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.220
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.099
Then all tps features from the old Tails version are active 1.178
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.699
And the expected persistent files created with the old Tails version are present in the filesystem 1.135
And all persistent directories from the old Tails version have safe access rights 1.946
After features/support/hooks.rb:339 0.769
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
4:6.225
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.972
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.539
When the network is plugged 0.017
And Tor is ready 12.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.124
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.806
Given I shutdown Tails and wait for the computer to power off 10.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.618
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.448
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
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.134
# 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.197
When the network is plugged 0.014
And Tor is ready 10.178
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.147
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.435
Given I shutdown Tails and wait for the computer to power off 8.504
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.889
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.214
And the file system changes introduced in version 6.3~testoverlayfs are present 0.367
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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.208
When the network is plugged 0.020
And Tor is ready 10.479
Then the Upgrader considers the system as up-to-date 10.509
# 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.336
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.416
After features/support/hooks.rb:339 0.929
After features/support/hooks.rb:108 0.098
Tags: @product @automatic_upgrade
22.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.264
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.106
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.356
After features/support/hooks.rb:339 0.700
After features/support/hooks.rb:108 0.000