Project Number Date
test_Tails_ISO_add-relevant-binary-packages-script 3 10 Oct 2026, 01:42

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 11:10.403 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.007
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.276
When I start Tails from USB drive "old" with network unplugged 54.230
Then the boot device has safe access rights 1.786
And Tails is running from USB drive "old" 0.216
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.541
After features/support/hooks.rb:108 0.006
Tags: @product
1:21.636
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 48.319
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 22.392
And I take note of which tps features are available 6.184
Then a Tails persistence partition exists on USB drive "old" 0.494
And I shutdown Tails and wait for the computer to power off 3.922
After features/support/hooks.rb:339 0.198
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.169
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.009
Then Tails is running from USB drive "old" 0.179
And all tps features are active 6.399
When I write some files expected to persist 1.042
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.123
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.433
And I take note of which tps features are available 6.325
And I shutdown Tails and wait for the computer to power off 3.936
# 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.365
After features/support/hooks.rb:339 0.103
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.551
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.256
And I log in to a new session 11.436
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.601
And I plug USB drive "to_upgrade" 2.203
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.153
Then the running Tails is installed on USB drive "to_upgrade" 17.664
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.621
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.331
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.115
Then all tps features from the old Tails version are active 0.945
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 1.769
And the expected persistent files created with the old Tails version are present in the filesystem 0.853
And all persistent directories from the old Tails version have safe access rights 1.342
After features/support/hooks.rb:339 0.827
After features/support/hooks.rb:108 0.005
3:21.515
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 8.200
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
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.176
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.291
When the network is plugged 0.033
And Tor is ready 12.742
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.321
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.408
Given I shutdown Tails and wait for the computer to power off 5.500
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.523
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.365
And the file system changes introduced in version 6.2~testoverlayfs are present 0.166
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.090
# 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.154
When the network is plugged 0.026
And Tor is ready 10.050
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.296
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.358
Given I shutdown Tails and wait for the computer to power off 5.006
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.619
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.462
And the file system changes introduced in version 6.3~testoverlayfs are present 0.297
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.039
And Tor is ready 9.976
Then the Upgrader considers the system as up-to-date 0.097
# 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.204
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.332
After features/support/hooks.rb:339 0.799
After features/support/hooks.rb:108 0.009
31.191
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 20.737
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.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.023
And Tor is ready 9.863
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.290
After features/support/hooks.rb:339 0.915
After features/support/hooks.rb:108 0.000