Project Number Date
test_Tails_ISO_stable 6201 13 Mar 2026, 11:13

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 13:18.974 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:23.174
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.070
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.695
When I start Tails from USB drive "old" with network unplugged 1:3.556
Then the boot device has safe access rights 3.015
And Tails is running from USB drive "old" 0.320
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:331 3.534
After features/support/hooks.rb:100 0.044
Tags: @product
1:32.581
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 1:0.264
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 26.156
And I take note of which tps features are available 0.846
Then a Tails persistence partition exists on USB drive "old" 0.625
And I shutdown Tails and wait for the computer to power off 4.283
After features/support/hooks.rb:331 0.269
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.197
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.182
Then Tails is running from USB drive "old" 0.346
And all tps features are active 1.221
When I write some files expected to persist 1.385
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.335
And all persistence configuration files have safe access rights 0.748
And all persistent directories from the old Tails version have safe access rights 2.556
And I take note of which tps features are available 0.270
And I shutdown Tails and wait for the computer to power off 8.305
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.791
After features/support/hooks.rb:331 0.154
After features/support/hooks.rb:100 0.008
Tags: @product
2:16.956
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.127
And I log in to a new session 13.020
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.922
And I plug USB drive "to_upgrade" 2.404
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.137
Then the running Tails is installed on USB drive "to_upgrade" 17.039
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:331 2.724
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.054
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.103
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.935
Then all tps features from the old Tails version are active 0.946
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 2.879
And the expected persistent files created with the old Tails version are present in the filesystem 1.372
And all persistent directories from the old Tails version have safe access rights 2.503
After features/support/hooks.rb:331 0.696
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:48.844
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 8.655
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.020
And Tor is ready 21.047
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.374
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.255
Given I shutdown Tails and wait for the computer to power off 19.637
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.830
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.467
And the file system changes introduced in version 6.2~testoverlayfs are present 0.334
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.203
# 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.232
When the network is plugged 0.014
And Tor is ready 22.544
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.440
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.298
Given I shutdown Tails and wait for the computer to power off 17.894
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.842
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.171
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.017
And Tor is ready 20.521
Then the Upgrader considers the system as up-to-date 0.117
# 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.718
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.377
After features/support/hooks.rb:331 0.661
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
28.164
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.520
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 19.822
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.469
After features/support/hooks.rb:331 0.710
After features/support/hooks.rb:100 0.000