Project Number Date
test_Tails_ISO_devel 4209 04 Feb 2026, 13:00

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 14:48.172 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:28.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 31.236
When I start Tails from USB drive "old" with network unplugged 51.963
Then the boot device has safe access rights 3.397
And Tails is running from USB drive "old" 0.384
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.310
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:331 5.125
After features/support/hooks.rb:100 0.020
Tags: @product
1:39.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login 1:4.863
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 29.324
And I take note of which tps features are available 1.195
Then a Tails persistence partition exists on USB drive "old" 0.663
And I shutdown Tails and wait for the computer to power off 3.038
After features/support/hooks.rb:331 0.369
After features/support/hooks.rb:100 0.012
Tags: @product
1:54.391
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:20.675
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.944
When I write some files expected to persist 1.543
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.384
And all persistent directories from the old Tails version have safe access rights 2.707
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 7.659
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.311
After features/support/hooks.rb:331 0.546
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.269
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 without a persistent partition and stopped at Tails Greeter's login screen 13.753
And I log in to a new session 14.282
And I clone USB drive "old" to a new USB drive "to_upgrade" 17.942
And I plug USB drive "to_upgrade" 2.822
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.096
Then the running Tails is installed on USB drive "to_upgrade" 20.929
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.255
After features/support/hooks.rb:331 3.835
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.485
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.358
Then all tps features from the old Tails version are active 2.057
And Tails is running from USB drive "to_upgrade" 0.333
And the boot device has safe access rights 2.932
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.210
After features/support/hooks.rb:331 0.885
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:55.147
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 18.155
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.056
And Tor is ready 13.584
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.697
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.312
Given I shutdown Tails and wait for the computer to power off 11.968
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.206
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.092
And the file system changes introduced in version 6.2~testoverlayfs are present 0.300
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.248
When the network is plugged 0.053
And Tor is ready 41.673
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.602
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.024
Given I shutdown Tails and wait for the computer to power off 7.634
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.704
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.937
And the file system changes introduced in version 6.3~testoverlayfs are present 0.448
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.056
And Tor is ready 12.230
Then the Upgrader considers the system as up-to-date 0.169
# 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 5.571
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.522
After features/support/hooks.rb:331 1.123
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
24.404
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 11.022
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.064
And Tor is ready 11.126
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.706
After features/support/hooks.rb:331 1.173
After features/support/hooks.rb:100 0.000