Project Number Date
test_Tails_ISO_stable 6331 29 Apr 2026, 07:35

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:45.605 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
57.589
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.458
When I start Tails from USB drive "old" with network unplugged 39.780
Then the boot device has safe access rights 2.620
And Tails is running from USB drive "old" 0.204
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:331 3.524
After features/support/hooks.rb:100 0.015
Tags: @product
1:25.267
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 53.871
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 23.135
And I take note of which tps features are available 0.639
Then a Tails persistence partition exists on USB drive "old" 0.537
And I shutdown Tails and wait for the computer to power off 6.767
After features/support/hooks.rb:331 0.591
After features/support/hooks.rb:100 0.007
Tags: @product
1:26.263
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.058
Then Tails is running from USB drive "old" 0.217
And all tps features are active 1.028
When I write some files expected to persist 1.233
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 1.802
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 8.007
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.086
After features/support/hooks.rb:331 0.568
After features/support/hooks.rb:100 0.007
Tags: @product
2:21.493
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 8.002
And I log in to a new session 16.881
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.767
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.263
Then the running Tails is installed on USB drive "to_upgrade" 16.067
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.166
After features/support/hooks.rb:331 5.616
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.499
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.085
Then all tps features from the old Tails version are active 0.952
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.442
And the expected persistent files created with the old Tails version are present in the filesystem 0.998
And all persistent directories from the old Tails version have safe access rights 1.720
After features/support/hooks.rb:331 0.762
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:55.504
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 8.450
And no SquashFS delta is installed 0.164
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
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.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.017
And Tor is ready 37.662
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.422
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.828
Given I shutdown Tails and wait for the computer to power off 33.774
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.518
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.196
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.193
When the network is plugged 0.015
And Tor is ready 13.113
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.718
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.826
Given I shutdown Tails and wait for the computer to power off 13.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.376
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.209
And the file system changes introduced in version 6.3~testoverlayfs are present 0.317
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.157
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.015
And Tor is ready 21.557
Then the Upgrader considers the system as up-to-date 0.101
# 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.390
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:331 0.882
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
30.987
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 7.544
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 22.651
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.404
After features/support/hooks.rb:331 0.738
After features/support/hooks.rb:100 0.000