Project Number Date
test_Tails_ISO_stable 6109 30 Jan 2026, 15:08

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:27.802 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:15.486
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.279
When I start Tails from USB drive "old" with network unplugged 57.632
Then the boot device has safe access rights 2.868
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:331 3.621
After features/support/hooks.rb:100 0.051
Tags: @product
1:19.473
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 50.968
Then Tails is running from USB drive "old" 0.341
And I create a persistent partition 24.194
And I take note of which tps features are available 0.689
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 2.698
After features/support/hooks.rb:331 0.389
After features/support/hooks.rb:100 0.006
Tags: @product
1:18.700
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.808
Then Tails is running from USB drive "old" 0.255
And all tps features are active 1.085
When I write some files expected to persist 1.219
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.294
And all persistent directories from the old Tails version have safe access rights 1.782
And I take note of which tps features are available 0.139
And I shutdown Tails and wait for the computer to power off 4.155
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.703
After features/support/hooks.rb:331 0.122
After features/support/hooks.rb:100 0.007
Tags: @product
2:6.907
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 7.837
And I log in to a new session 9.811
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.697
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.833
Then the running Tails is installed on USB drive "to_upgrade" 14.198
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:331 2.080
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.856
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.091
Then all tps features from the old Tails version are active 1.047
And Tails is running from USB drive "to_upgrade" 0.192
And the boot device has safe access rights 2.635
And the expected persistent files created with the old Tails version are present in the filesystem 1.085
And all persistent directories from the old Tails version have safe access rights 1.755
After features/support/hooks.rb:331 0.836
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:1.063
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.043
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.186
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.016
And Tor is ready 13.222
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.346
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.961
Given I shutdown Tails and wait for the computer to power off 9.524
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.089
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.115
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.114
# 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.202
When the network is plugged 0.016
And Tor is ready 40.767
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.072
Given I shutdown Tails and wait for the computer to power off 7.843
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.567
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.011
And the file system changes introduced in version 6.3~testoverlayfs are present 0.324
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.178
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.017
And Tor is ready 10.934
Then the Upgrader considers the system as up-to-date 10.525
# 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.080
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.322
After features/support/hooks.rb:331 0.844
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
19.314
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.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 8.431
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.024
After features/support/hooks.rb:331 0.929
After features/support/hooks.rb:100 0.000