Project Number Date
test_Tails_ISO_devel 4663 07 Oct 2026, 14:12

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:4.074 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:8.118
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 13.829
When I start Tails from USB drive "old" with network unplugged 50.358
Then the boot device has safe access rights 2.097
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.422
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.382
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 50.695
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 24.196
And I take note of which tps features are available 8.509
Then a Tails persistence partition exists on USB drive "old" 0.560
And I shutdown Tails and wait for the computer to power off 4.070
After features/support/hooks.rb:339 0.622
After features/support/hooks.rb:108 0.016
Tags: @product
1:40.338
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.132
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.420
Then Tails is running from USB drive "old" 0.243
And all tps features are active 9.357
When I write some files expected to persist 1.192
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.253
And all persistent directories from the old Tails version have safe access rights 1.562
And I take note of which tps features are available 7.013
And I shutdown Tails and wait for the computer to power off 3.982
# 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.014
After features/support/hooks.rb:339 0.498
After features/support/hooks.rb:108 0.007
Tags: @product
2:28.475
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 22.562
And I log in to a new session 11.763
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.710
And I plug USB drive "to_upgrade" 2.336
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.067
Then the running Tails is installed on USB drive "to_upgrade" 18.771
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 1.516
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.056
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.651
Then all tps features from the old Tails version are active 1.078
And Tails is running from USB drive "to_upgrade" 0.199
And the boot device has safe access rights 2.472
And the expected persistent files created with the old Tails version are present in the filesystem 1.606
And all persistent directories from the old Tails version have safe access rights 1.965
After features/support/hooks.rb:339 0.696
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
3:35.340
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.752
And no SquashFS delta is installed 0.218
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.038
And Tor is ready 12.433
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.607
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.552
Given I shutdown Tails and wait for the computer to power off 5.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.294
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.897
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.159
When the network is plugged 0.027
And Tor is ready 11.015
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.330
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.811
Given I shutdown Tails and wait for the computer to power off 5.164
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.467
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.468
And the file system changes introduced in version 6.3~testoverlayfs are present 0.443
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.029
And Tor is ready 10.689
Then the Upgrader considers the system as up-to-date 0.109
# 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 3.636
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:339 0.928
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
32.362
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.329
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
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.045
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 8.646
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.000
After features/support/hooks.rb:339 0.799
After features/support/hooks.rb:108 0.000