Project Number Date
test_Tails_ISO_stable 5997 10 Dec 2025, 11:48

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 16:58.879 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
2:15.617
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.204
And I create a 7200 MiB disk named "old" 0.066
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 34.463
When I start Tails from USB drive "old" with network unplugged 1:33.905
Then the boot device has safe access rights 4.950
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:331 4.116
After features/support/hooks.rb:100 0.009
Tags: @product
2:11.408
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:29.608
Then Tails is running from USB drive "old" 0.396
And I create a persistent partition 31.065
And I take note of which tps features are available 1.306
Then a Tails persistence partition exists on USB drive "old" 0.724
And I shutdown Tails and wait for the computer to power off 8.119
After features/support/hooks.rb:331 0.711
After features/support/hooks.rb:100 0.010
Tags: @product
2:22.851
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:45.386
Then Tails is running from USB drive "old" 0.679
And all tps features are active 1.909
When I write some files expected to persist 1.755
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.273
And all persistence configuration files have safe access rights 0.431
And all persistent directories from the old Tails version have safe access rights 2.372
And I take note of which tps features are available 0.737
And I shutdown Tails and wait for the computer to power off 9.077
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.992
After features/support/hooks.rb:331 0.622
After features/support/hooks.rb:100 0.009
Tags: @product
2:44.091
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.233
And I log in to a new session 18.731
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.701
And I plug USB drive "to_upgrade" 2.634
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.777
Then the running Tails is installed on USB drive "to_upgrade" 21.584
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:331 3.971
After features/support/hooks.rb:100 0.000
Tags: @product
1:30.882
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.792
Then all tps features from the old Tails version are active 2.134
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.528
And the expected persistent files created with the old Tails version are present in the filesystem 1.338
And all persistent directories from the old Tails version have safe access rights 2.597
After features/support/hooks.rb:331 1.119
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:27.119
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.255
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.413
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.577
When the network is plugged 0.062
And Tor is ready 32.729
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.616
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.275
Given I shutdown Tails and wait for the computer to power off 11.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.453
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.962
And the file system changes introduced in version 6.2~testoverlayfs are present 0.373
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.184
# 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.536
When the network is plugged 0.065
And Tor is ready 41.257
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.869
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.788
Given I shutdown Tails and wait for the computer to power off 10.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.907
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.603
And the file system changes introduced in version 6.3~testoverlayfs are present 0.521
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.051
And Tor is ready 12.035
Then the Upgrader considers the system as up-to-date 0.146
# 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 6.092
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.465
After features/support/hooks.rb:331 0.857
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
26.908
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 with a persistent partition enabled and logged in 12.449
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.062
And Tor is ready 11.881
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.095
After features/support/hooks.rb:331 1.063
After features/support/hooks.rb:100 0.000