Project Number Date
test_Tails_ISO_devel 4400 17 May 2026, 11:09

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:0.654 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:0.945
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 12.829
When I start Tails from USB drive "old" with network unplugged 43.971
Then the boot device has safe access rights 2.342
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:335 3.624
After features/support/hooks.rb:104 0.007
Tags: @product
1:25.409
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 52.519
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 23.585
And I take note of which tps features are available 0.331
Then a Tails persistence partition exists on USB drive "old" 0.539
And I shutdown Tails and wait for the computer to power off 8.144
After features/support/hooks.rb:335 0.462
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.971
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.938
Then Tails is running from USB drive "old" 0.271
And all tps features are active 1.111
When I write some files expected to persist 1.221
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.357
And all persistent directories from the old Tails version have safe access rights 1.977
And I take note of which tps features are available 0.184
And I shutdown Tails and wait for the computer to power off 7.994
# 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.639
After features/support/hooks.rb:335 0.394
After features/support/hooks.rb:104 0.006
Tags: @product
2:8.947
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.617
And I log in to a new session 11.573
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.707
And I plug USB drive "to_upgrade" 2.212
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.114
Then the running Tails is installed on USB drive "to_upgrade" 15.462
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:335 1.986
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.741
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.039
Then all tps features from the old Tails version are active 1.012
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.459
And the expected persistent files created with the old Tails version are present in the filesystem 1.071
And all persistent directories from the old Tails version have safe access rights 1.852
After features/support/hooks.rb:335 1.032
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:35.225
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.305
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.019
And Tor is ready 13.306
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.526
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.317
Given I shutdown Tails and wait for the computer to power off 9.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.944
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 1.173
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.206
When the network is plugged 0.014
And Tor is ready 9.604
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.047
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.419
Given I shutdown Tails and wait for the computer to power off 8.068
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.139
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.127
And the file system changes introduced in version 6.3~testoverlayfs are present 0.350
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.012
And Tor is ready 9.718
Then the Upgrader considers the system as up-to-date 10.508
# 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.826
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.353
After features/support/hooks.rb:335 0.754
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
19.413
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.273
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.443
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.372
After features/support/hooks.rb:335 0.814
After features/support/hooks.rb:104 0.000