Project Number Date
test_Tails_ISO_devel 4299 28 Mar 2026, 07:41

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:29.880 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:13.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.767
When I start Tails from USB drive "old" with network unplugged 55.482
Then the boot device has safe access rights 2.687
And Tails is running from USB drive "old" 0.258
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:331 3.412
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.285
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 53.368
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 25.164
And I take note of which tps features are available 0.872
Then a Tails persistence partition exists on USB drive "old" 0.731
And I shutdown Tails and wait for the computer to power off 6.760
After features/support/hooks.rb:331 0.633
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.193
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.093
When I write some files expected to persist 1.275
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.497
And all persistent directories from the old Tails version have safe access rights 2.084
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 4.179
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.878
After features/support/hooks.rb:331 0.538
After features/support/hooks.rb:100 0.015
Tags: @product
2:11.111
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 without a persistent partition and stopped at Tails Greeter's login screen 7.800
And I log in to a new session 12.111
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.776
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.977
Then the running Tails is installed on USB drive "to_upgrade" 15.918
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:331 2.066
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.243
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 1:4.104
Then all tps features from the old Tails version are active 0.926
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.670
And the expected persistent files created with the old Tails version are present in the filesystem 1.286
And all persistent directories from the old Tails version have safe access rights 1.967
After features/support/hooks.rb:331 0.510
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
4:36.505
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.734
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.394
When the network is plugged 0.019
And Tor is ready 21.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.365
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.234
Given I shutdown Tails and wait for the computer to power off 20.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.351
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.104
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
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.124
# 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.186
When the network is plugged 0.016
And Tor is ready 21.784
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.363
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.645
Given I shutdown Tails and wait for the computer to power off 12.196
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.412
Then Tails is running version 6.3~testoverlayfs 0.031
And all tps features are active 1.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.393
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.209
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.015
And Tor is ready 22.347
Then the Upgrader considers the system as up-to-date 0.127
# 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.240
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:331 0.994
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.135
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.544
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.091
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 17.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.407
After features/support/hooks.rb:331 0.621
After features/support/hooks.rb:100 0.000