Project Number Date
test_Tails_ISO_add-relevant-binary-packages-script 2 09 Oct 2026, 01:44

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 10:58.909 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:11.430
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.068
When I start Tails from USB drive "old" with network unplugged 54.341
Then the boot device has safe access rights 2.353
And Tails is running from USB drive "old" 0.188
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.144
After features/support/hooks.rb:108 0.006
Tags: @product
1:19.921
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 48.069
Then Tails is running from USB drive "old" 0.208
And I create a persistent partition 22.858
And I take note of which tps features are available 5.695
Then a Tails persistence partition exists on USB drive "old" 0.463
And I shutdown Tails and wait for the computer to power off 2.539
After features/support/hooks.rb:339 0.434
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.254
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.626
Then Tails is running from USB drive "old" 0.218
And all tps features are active 7.418
When I write some files expected to persist 1.019
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.114
And all persistence configuration files have safe access rights 0.216
And all persistent directories from the old Tails version have safe access rights 1.514
And I take note of which tps features are available 5.892
And I shutdown Tails and wait for the computer to power off 2.512
# 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" 11.508
After features/support/hooks.rb:339 0.565
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.967
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 without a persistent partition and stopped at Tails Greeter's login screen 8.099
And I log in to a new session 12.040
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.630
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.162
Then the running Tails is installed on USB drive "to_upgrade" 17.555
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.645
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.625
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.061
Then all tps features from the old Tails version are active 0.991
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 1.904
And the expected persistent files created with the old Tails version are present in the filesystem 0.809
And all persistent directories from the old Tails version have safe access rights 1.578
After features/support/hooks.rb:339 0.570
After features/support/hooks.rb:108 0.005
3:21.209
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 7.877
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.030
And Tor is ready 12.304
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.290
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.172
Given I shutdown Tails and wait for the computer to power off 5.430
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.624
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.797
And the file system changes introduced in version 6.2~testoverlayfs are present 0.200
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.227
When the network is plugged 0.035
And Tor is ready 10.700
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.312
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.596
Given I shutdown Tails and wait for the computer to power off 2.546
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.411
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.417
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.098
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.161
When the network is plugged 0.024
And Tor is ready 10.084
Then the Upgrader considers the system as up-to-date 0.115
# 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 2.948
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:339 0.539
After features/support/hooks.rb:108 0.015
18.499
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 7.519
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
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.028
And Tor is ready 9.809
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.847
After features/support/hooks.rb:339 0.629
After features/support/hooks.rb:108 0.000