Project Number Date
test_Tails_ISO_21644-desktop-file-dirs-mount-monitoring 6 13 Aug 2026, 10:43

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:15.651 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:21.983
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.088
When I start Tails from USB drive "old" with network unplugged 1:5.114
Then the boot device has safe access rights 2.122
And Tails is running from USB drive "old" 0.168
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.030
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.627
After features/support/hooks.rb:108 0.027
Tags: @product
1:19.808
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 46.579
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 23.278
And I take note of which tps features are available 6.496
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 2.556
After features/support/hooks.rb:339 0.494
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.875
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.535
Then Tails is running from USB drive "old" 0.194
And all tps features are active 6.755
When I write some files expected to persist 1.131
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.294
And all persistent directories from the old Tails version have safe access rights 1.747
And I take note of which tps features are available 6.295
And I shutdown Tails and wait for the computer to power off 2.569
# 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.122
After features/support/hooks.rb:339 0.401
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.438
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 without a persistent partition and stopped at Tails Greeter's login screen 8.204
And I log in to a new session 10.928
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.643
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.822
Then the running Tails is installed on USB drive "to_upgrade" 17.359
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.807
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.728
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.780
Then all tps features from the old Tails version are active 0.996
And Tails is running from USB drive "to_upgrade" 0.176
And the boot device has safe access rights 2.234
And the expected persistent files created with the old Tails version are present in the filesystem 0.816
And all persistent directories from the old Tails version have safe access rights 1.643
After features/support/hooks.rb:339 0.893
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:30.132
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.210
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.271
When the network is plugged 0.028
And Tor is ready 13.142
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.901
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.161
Given I shutdown Tails and wait for the computer to power off 6.466
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.020
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.470
And the file system changes introduced in version 6.2~testoverlayfs are present 0.212
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.238
When the network is plugged 0.038
And Tor is ready 10.115
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.535
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.775
Given I shutdown Tails and wait for the computer to power off 4.130
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.477
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.604
And the file system changes introduced in version 6.3~testoverlayfs are present 0.279
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.171
When the network is plugged 0.025
And Tor is ready 10.295
Then the Upgrader considers the system as up-to-date 0.143
# 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.143
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:339 0.683
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
18.684
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.873
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
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.026
And Tor is ready 8.337
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.099
After features/support/hooks.rb:339 0.979
After features/support/hooks.rb:108 0.000