Project Number Date
test_Tails_ISO_stable 6239 27 Mar 2026, 06:59

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 12:0.779 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:19.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.338
When I start Tails from USB drive "old" with network unplugged 1:1.390
Then the boot device has safe access rights 2.632
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:331 3.671
After features/support/hooks.rb:100 0.007
Tags: @product
1:19.162
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 52.238
Then Tails is running from USB drive "old" 0.214
And I create a persistent partition 22.813
And I take note of which tps features are available 0.690
Then a Tails persistence partition exists on USB drive "old" 0.479
And I shutdown Tails and wait for the computer to power off 2.666
After features/support/hooks.rb:331 0.209
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.480
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.454
Then Tails is running from USB drive "old" 0.236
And all tps features are active 1.021
When I write some files expected to persist 1.174
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.410
And all persistent directories from the old Tails version have safe access rights 1.897
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 8.273
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.630
After features/support/hooks.rb:331 0.349
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.602
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.527
And I log in to a new session 11.380
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.816
And I plug USB drive "to_upgrade" 2.257
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.254
Then the running Tails is installed on USB drive "to_upgrade" 15.074
And I unplug USB drive "to_upgrade" 0.164
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:331 2.227
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.941
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.611
Then all tps features from the old Tails version are active 0.961
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.389
And the expected persistent files created with the old Tails version are present in the filesystem 0.983
And all persistent directories from the old Tails version have safe access rights 1.683
After features/support/hooks.rb:331 0.761
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:17.607
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.990
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.314
When the network is plugged 0.019
And Tor is ready 22.052
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.347
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.570
Given I shutdown Tails and wait for the computer to power off 14.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.718
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.066
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
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.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.223
When the network is plugged 0.060
And Tor is ready 20.113
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.383
Given I shutdown Tails and wait for the computer to power off 17.088
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.468
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 0.963
And the file system changes introduced in version 6.3~testoverlayfs are present 0.308
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.013
And Tor is ready 14.946
Then the Upgrader considers the system as up-to-date 0.114
# 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 4.113
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:331 0.844
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
25.905
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.498
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
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.053
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 17.549
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.439
After features/support/hooks.rb:331 0.812
After features/support/hooks.rb:100 0.000