Project Number Date
test_Tails_ISO_stable 6419 03 Jun 2026, 07:22

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:1.950 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.717
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.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.143
When I start Tails from USB drive "old" with network unplugged 43.230
Then the boot device has safe access rights 2.570
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:335 3.408
After features/support/hooks.rb:104 0.007
Tags: @product
1:25.940
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 52.380
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 24.156
And I take note of which tps features are available 0.370
Then a Tails persistence partition exists on USB drive "old" 0.473
And I shutdown Tails and wait for the computer to power off 8.233
After features/support/hooks.rb:335 0.460
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.426
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.594
Then Tails is running from USB drive "old" 0.238
And all tps features are active 1.100
When I write some files expected to persist 1.190
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 2.034
And I take note of which tps features are available 0.171
And I shutdown Tails and wait for the computer to power off 7.876
# 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.651
After features/support/hooks.rb:335 0.395
After features/support/hooks.rb:104 0.007
Tags: @product
2:9.180
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.582
And I log in to a new session 12.049
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.721
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.221
Then the running Tails is installed on USB drive "to_upgrade" 15.080
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:335 3.421
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.696
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.846
Then all tps features from the old Tails version are active 0.942
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.560
And the expected persistent files created with the old Tails version are present in the filesystem 1.035
And all persistent directories from the old Tails version have safe access rights 2.033
After features/support/hooks.rb:335 0.555
After features/support/hooks.rb:104 0.007
3:34.393
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.239
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
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.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.016
And Tor is ready 11.974
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.514
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.631
Given I shutdown Tails and wait for the computer to power off 9.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.186
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.209
When the network is plugged 0.014
And Tor is ready 10.031
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.753
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.142
Given I shutdown Tails and wait for the computer to power off 8.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.712
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.095
And the file system changes introduced in version 6.3~testoverlayfs are present 0.328
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.018
And Tor is ready 10.434
Then the Upgrader considers the system as up-to-date 10.552
# 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.828
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.384
After features/support/hooks.rb:335 1.016
After features/support/hooks.rb:104 0.011
19.594
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.319
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.041
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.430
After features/support/hooks.rb:335 0.633
After features/support/hooks.rb:104 0.000