Project Number Date
test_Tails_ISO_add-relevant-binary-packages-script 5 12 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:55.685 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:4.773
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.031
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.075
When I start Tails from USB drive "old" with network unplugged 48.141
Then the boot device has safe access rights 1.882
And Tails is running from USB drive "old" 0.201
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.025
And udev-watchdog is monitoring the correct device 0.142
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 1.716
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.827
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 47.851
Then Tails is running from USB drive "old" 0.174
And I create a persistent partition 23.199
And I take note of which tps features are available 6.832
Then a Tails persistence partition exists on USB drive "old" 0.536
And I shutdown Tails and wait for the computer to power off 4.163
After features/support/hooks.rb:339 0.551
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.984
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.437
Then Tails is running from USB drive "old" 0.218
And all tps features are active 6.850
When I write some files expected to persist 1.008
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.363
And I take note of which tps features are available 6.045
And I shutdown Tails and wait for the computer to power off 2.531
# 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.009
After features/support/hooks.rb:339 0.287
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.955
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.136
And I log in to a new session 11.084
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.650
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.750
Then the running Tails is installed on USB drive "to_upgrade" 17.884
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.666
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.289
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.763
Then all tps features from the old Tails version are active 1.101
And Tails is running from USB drive "to_upgrade" 0.198
And the boot device has safe access rights 2.290
And the expected persistent files created with the old Tails version are present in the filesystem 1.132
And all persistent directories from the old Tails version have safe access rights 1.731
After features/support/hooks.rb:339 0.965
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
3:26.683
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.426
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.034
And Tor is ready 12.520
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.951
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.591
Given I shutdown Tails and wait for the computer to power off 5.589
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.150
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.710
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.157
When the network is plugged 0.031
And Tor is ready 10.269
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.307
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.996
Given I shutdown Tails and wait for the computer to power off 3.804
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.887
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.665
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.149
When the network is plugged 0.025
And Tor is ready 10.045
Then the Upgrader considers the system as up-to-date 0.075
# 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.119
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.315
After features/support/hooks.rb:339 0.543
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
17.172
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.662
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.189
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 8.898
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.305
After features/support/hooks.rb:339 0.962
After features/support/hooks.rb:108 0.000