Project Number Date
test_Tails_ISO_devel 4437 08 Jun 2026, 11:05

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:59.353 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:3.506
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.056
When I start Tails from USB drive "old" with network unplugged 45.843
Then the boot device has safe access rights 2.797
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:335 3.640
After features/support/hooks.rb:104 0.007
Tags: @product
1:25.442
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 51.650
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 24.434
And I take note of which tps features are available 0.321
Then a Tails persistence partition exists on USB drive "old" 0.505
And I shutdown Tails and wait for the computer to power off 8.230
After features/support/hooks.rb:335 0.409
After features/support/hooks.rb:104 0.007
Tags: @product
1:23.016
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.386
Then Tails is running from USB drive "old" 0.197
And all tps features are active 1.041
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.121
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 1.817
And I take note of which tps features are available 0.174
And I shutdown Tails and wait for the computer to power off 8.251
# 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.566
After features/support/hooks.rb:335 0.279
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.954
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.978
And I log in to a new session 12.136
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.718
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.918
Then the running Tails is installed on USB drive "to_upgrade" 14.683
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:335 1.867
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.480
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.118
Then all tps features from the old Tails version are active 0.981
And Tails is running from USB drive "to_upgrade" 0.200
And the boot device has safe access rights 2.363
And the expected persistent files created with the old Tails version are present in the filesystem 1.004
And all persistent directories from the old Tails version have safe access rights 1.761
After features/support/hooks.rb:335 0.730
After features/support/hooks.rb:104 0.006
3:32.025
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.992
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.346
When the network is plugged 0.013
And Tor is ready 13.128
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.309
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.730
Given I shutdown Tails and wait for the computer to power off 9.510
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.293
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.019
And the file system changes introduced in version 6.2~testoverlayfs are present 0.188
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.189
When the network is plugged 0.018
And Tor is ready 10.135
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.745
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.083
Given I shutdown Tails and wait for the computer to power off 7.830
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.286
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.147
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.235
When the network is plugged 0.017
And Tor is ready 10.875
Then the Upgrader considers the system as up-to-date 10.476
# 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.776
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.338
After features/support/hooks.rb:335 0.875
After features/support/hooks.rb:104 0.011
18.927
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.240
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.459
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.860
After features/support/hooks.rb:335 0.827
After features/support/hooks.rb:104 0.000