Project Number Date
test_Tails_ISO_devel 4241 18 Feb 2026, 20:03

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:24.114 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:3.177
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.111
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.084
When I start Tails from USB drive "old" with network unplugged 44.366
Then the boot device has safe access rights 2.818
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.035
And process "udev-watchdog" is running 0.125
And udev-watchdog is monitoring the correct device 0.269
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:331 3.415
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.981
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 54.455
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 24.533
And I take note of which tps features are available 0.796
Then a Tails persistence partition exists on USB drive "old" 0.642
And I shutdown Tails and wait for the computer to power off 8.205
After features/support/hooks.rb:331 0.377
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.440
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.307
Then Tails is running from USB drive "old" 0.240
And all tps features are active 1.128
When I write some files expected to persist 1.273
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 2.074
And I take note of which tps features are available 0.204
And I shutdown Tails and wait for the computer to power off 8.402
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.239
After features/support/hooks.rb:331 0.416
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.519
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 without a persistent partition and stopped at Tails Greeter's login screen 8.639
And I log in to a new session 10.183
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.756
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.429
Then the running Tails is installed on USB drive "to_upgrade" 15.989
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 2.179
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.686
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.125
Then all tps features from the old Tails version are active 1.031
And Tails is running from USB drive "to_upgrade" 0.337
And the boot device has safe access rights 2.769
And the expected persistent files created with the old Tails version are present in the filesystem 1.093
And all persistent directories from the old Tails version have safe access rights 2.261
After features/support/hooks.rb:331 0.574
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:36.377
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.303
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.032
And Tor is ready 20.471
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.418
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.308
Given I shutdown Tails and wait for the computer to power off 20.267
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.985
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.125
And the file system changes introduced in version 6.2~testoverlayfs are present 0.349
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.274
When the network is plugged 0.021
And Tor is ready 21.597
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.524
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.708
Given I shutdown Tails and wait for the computer to power off 17.505
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.639
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.166
And the file system changes introduced in version 6.3~testoverlayfs are present 0.384
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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.015
And Tor is ready 20.768
Then the Upgrader considers the system as up-to-date 0.108
# 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.395
After features/support/hooks.rb:331 1.035
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
24.931
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.324
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 16.814
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.411
After features/support/hooks.rb:331 0.859
After features/support/hooks.rb:100 0.000