Project Number Date
test_Tails_ISO_stable 6166 24 Feb 2026, 22:39

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 13:23.154 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:44.653
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.951
When I start Tails from USB drive "old" with network unplugged 1:26.022
Then the boot device has safe access rights 2.805
And Tails is running from USB drive "old" 0.214
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:331 1.450
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 55.167
Then Tails is running from USB drive "old" 0.289
And I create a persistent partition 23.884
And I take note of which tps features are available 0.849
Then a Tails persistence partition exists on USB drive "old" 0.633
And I shutdown Tails and wait for the computer to power off 7.996
After features/support/hooks.rb:331 0.499
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.767
Then Tails is running from USB drive "old" 0.253
And all tps features are active 1.344
When I write some files expected to persist 1.615
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.119
And I take note of which tps features are available 0.170
And I shutdown Tails and wait for the computer to power off 8.289
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.819
After features/support/hooks.rb:331 0.353
After features/support/hooks.rb:100 0.006
Tags: @product
2:14.978
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.225
And I log in to a new session 13.884
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.740
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.901
Then the running Tails is installed on USB drive "to_upgrade" 16.706
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:331 3.720
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.599
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.893
Then all tps features from the old Tails version are active 0.998
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.388
And the expected persistent files created with the old Tails version are present in the filesystem 1.105
And all persistent directories from the old Tails version have safe access rights 1.917
After features/support/hooks.rb:331 0.663
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:37.187
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.695
And no SquashFS delta is installed 0.171
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.505
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.067
And Tor is ready 23.783
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.374
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.648
Given I shutdown Tails and wait for the computer to power off 15.924
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.752
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.252
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# 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.199
When the network is plugged 0.017
And Tor is ready 21.500
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.440
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.796
Given I shutdown Tails and wait for the computer to power off 17.427
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.208
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.192
And the file system changes introduced in version 6.3~testoverlayfs are present 0.403
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.016
And Tor is ready 21.573
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.155
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.361
After features/support/hooks.rb:331 0.776
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
38.790
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 20.436
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 17.647
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.352
After features/support/hooks.rb:331 0.933
After features/support/hooks.rb:100 0.000