Project Number Date
test_Tails_ISO_stable 6049 09 Jan 2026, 11:38

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:42.209 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.526
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.801
When I start Tails from USB drive "old" with network unplugged 55.030
Then the boot device has safe access rights 2.855
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.875
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.181
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 53.606
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 23.957
And I take note of which tps features are available 0.736
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 7.975
After features/support/hooks.rb:331 0.205
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.370
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.195
Then Tails is running from USB drive "old" 0.233
And all tps features are active 1.133
When I write some files expected to persist 1.590
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.254
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 2.006
And I take note of which tps features are available 0.169
And I shutdown Tails and wait for the computer to power off 6.967
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.427
After features/support/hooks.rb:331 0.459
After features/support/hooks.rb:100 0.006
Tags: @product
2:13.423
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 8.796
And I log in to a new session 12.838
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.954
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.660
Then the running Tails is installed on USB drive "to_upgrade" 16.687
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:331 3.738
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.637
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.887
Then all tps features from the old Tails version are active 1.072
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 2.935
And the expected persistent files created with the old Tails version are present in the filesystem 1.372
And all persistent directories from the old Tails version have safe access rights 2.035
After features/support/hooks.rb:331 0.619
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
3:49.117
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 8.517
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.351
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.022
And Tor is ready 13.648
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.650
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.723
Given I shutdown Tails and wait for the computer to power off 6.803
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.837
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.235
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.209
When the network is plugged 0.018
And Tor is ready 11.793
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.441
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.441
Given I shutdown Tails and wait for the computer to power off 8.054
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.378
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.167
And the file system changes introduced in version 6.3~testoverlayfs are present 0.422
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.017
And Tor is ready 11.183
Then the Upgrader considers the system as up-to-date 10.571
# 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.545
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.391
After features/support/hooks.rb:331 0.853
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
20.953
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.594
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 11.854
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.157
After features/support/hooks.rb:331 0.836
After features/support/hooks.rb:100 0.000