Project Number Date
test_Tails_ISO_devel 4382 08 May 2026, 10:55

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.380 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.415
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
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" 12.776
When I start Tails from USB drive "old" with network unplugged 40.321
Then the boot device has safe access rights 2.588
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.149
After features/support/hooks.rb:331 3.674
After features/support/hooks.rb:100 0.036
Tags: @product
1:21.450
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 51.428
Then Tails is running from USB drive "old" 0.200
And I create a persistent partition 24.357
And I take note of which tps features are available 0.631
Then a Tails persistence partition exists on USB drive "old" 0.520
And I shutdown Tails and wait for the computer to power off 4.250
After features/support/hooks.rb:331 0.437
After features/support/hooks.rb:100 0.006
Tags: @product
1:18.897
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.659
Then Tails is running from USB drive "old" 0.254
And all tps features are active 1.160
When I write some files expected to persist 1.256
# 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.414
And all persistent directories from the old Tails version have safe access rights 1.686
And I take note of which tps features are available 0.147
And I shutdown Tails and wait for the computer to power off 4.157
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.907
After features/support/hooks.rb:331 0.464
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.923
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.475
And I log in to a new session 12.118
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.724
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.849
Then the running Tails is installed on USB drive "to_upgrade" 15.273
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:331 2.057
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.557
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.782
Then all tps features from the old Tails version are active 1.015
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.429
And the expected persistent files created with the old Tails version are present in the filesystem 1.151
And all persistent directories from the old Tails version have safe access rights 1.912
After features/support/hooks.rb:331 0.719
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:23.251
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.178
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.016
And Tor is ready 19.799
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.375
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.924
Given I shutdown Tails and wait for the computer to power off 19.838
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.034
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 0.975
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.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.225
When the network is plugged 0.014
And Tor is ready 20.800
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.344
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.917
Given I shutdown Tails and wait for the computer to power off 13.296
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.606
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.035
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.119
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.169
When the network is plugged 0.014
And Tor is ready 21.095
Then the Upgrader considers the system as up-to-date 0.100
# 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.114
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.431
After features/support/hooks.rb:331 0.690
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
25.884
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.195
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 17.967
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.402
After features/support/hooks.rb:331 0.896
After features/support/hooks.rb:100 0.000