Project Number Date
test_Tails_ISO_stable 6196 12 Mar 2026, 11:21

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:39.739 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:31.736
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.015
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.567
When I start Tails from USB drive "old" with network unplugged 1:12.211
Then the boot device has safe access rights 3.072
And Tails is running from USB drive "old" 0.280
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.473
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.798
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login 57.640
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 25.489
And I take note of which tps features are available 0.732
Then a Tails persistence partition exists on USB drive "old" 0.572
And I shutdown Tails and wait for the computer to power off 7.054
After features/support/hooks.rb:331 0.599
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.771
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.453
Then Tails is running from USB drive "old" 0.228
And all tps features are active 1.148
When I write some files expected to persist 1.405
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.462
And all persistent directories from the old Tails version have safe access rights 2.186
And I take note of which tps features are available 0.169
And I shutdown Tails and wait for the computer to power off 4.448
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.997
After features/support/hooks.rb:331 0.527
After features/support/hooks.rb:100 0.010
Tags: @product
2:25.345
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 9.616
And I log in to a new session 14.717
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.268
And I plug USB drive "to_upgrade" 2.319
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.835
Then the running Tails is installed on USB drive "to_upgrade" 18.263
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.166
After features/support/hooks.rb:331 2.797
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.105
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.380
Then all tps features from the old Tails version are active 1.114
And Tails is running from USB drive "to_upgrade" 0.275
And the boot device has safe access rights 3.152
And the expected persistent files created with the old Tails version are present in the filesystem 1.323
And all persistent directories from the old Tails version have safe access rights 2.387
After features/support/hooks.rb:331 0.742
After features/support/hooks.rb:100 0.010
4:56.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.741
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
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.203
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.016
And Tor is ready 26.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.508
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.489
Given I shutdown Tails and wait for the computer to power off 21.266
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.417
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.469
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.173
# 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.253
When the network is plugged 0.016
And Tor is ready 21.018
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.545
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.984
Given I shutdown Tails and wait for the computer to power off 17.855
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.382
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.278
And the file system changes introduced in version 6.3~testoverlayfs are present 0.407
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.019
And Tor is ready 22.417
Then the Upgrader considers the system as up-to-date 0.111
# 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.216
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.415
After features/support/hooks.rb:331 0.758
After features/support/hooks.rb:100 0.018
28.585
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 8.345
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
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.069
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 19.437
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.408
After features/support/hooks.rb:331 0.670
After features/support/hooks.rb:100 0.000