Project Number Date
test_Tails_ISO_devel 4262 02 Mar 2026, 11:44

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:32.816 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:9.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.957
When I start Tails from USB drive "old" with network unplugged 50.147
Then the boot device has safe access rights 3.212
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 3.475
After features/support/hooks.rb:100 0.029
Tags: @product
1:25.026
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 55.066
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 25.542
And I take note of which tps features are available 0.656
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 2.856
After features/support/hooks.rb:331 0.390
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.553
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.254
Then Tails is running from USB drive "old" 0.315
And all tps features are active 1.229
When I write some files expected to persist 1.278
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.540
And all persistent directories from the old Tails version have safe access rights 2.133
And I take note of which tps features are available 0.187
And I shutdown Tails and wait for the computer to power off 7.883
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.486
After features/support/hooks.rb:331 0.337
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.290
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.271
And I log in to a new session 11.482
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.970
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.781
Then the running Tails is installed on USB drive "to_upgrade" 16.255
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 2.297
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.701
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.224
Then all tps features from the old Tails version are active 1.094
And Tails is running from USB drive "to_upgrade" 0.221
And the boot device has safe access rights 2.770
And the expected persistent files created with the old Tails version are present in the filesystem 1.198
And all persistent directories from the old Tails version have safe access rights 2.106
After features/support/hooks.rb:331 0.571
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:39.981
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.398
And no SquashFS delta is installed 0.112
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.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.459
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.035
And Tor is ready 21.661
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.390
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.493
Given I shutdown Tails and wait for the computer to power off 19.030
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.030
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 1.212
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.215
When the network is plugged 0.017
And Tor is ready 22.051
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.366
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.481
Given I shutdown Tails and wait for the computer to power off 17.661
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.829
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.339
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.015
And Tor is ready 21.262
Then the Upgrader considers the system as up-to-date 0.097
# 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.382
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.434
After features/support/hooks.rb:331 1.097
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
27.157
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.618
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.784
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.408
After features/support/hooks.rb:331 0.822
After features/support/hooks.rb:100 0.000