Project Number Date
test_Tails_ISO_stable 6345 02 May 2026, 07:15

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:33.222 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:4.221
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.518
When I start Tails from USB drive "old" with network unplugged 45.993
Then the boot device has safe access rights 2.922
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 1.218
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.420
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 54.549
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 25.603
And I take note of which tps features are available 0.802
Then a Tails persistence partition exists on USB drive "old" 0.575
And I shutdown Tails and wait for the computer to power off 8.552
After features/support/hooks.rb:331 0.452
After features/support/hooks.rb:100 0.016
Tags: @product
1:24.782
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.162
Then Tails is running from USB drive "old" 0.264
And all tps features are active 1.048
When I write some files expected to persist 1.231
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 2.089
And I take note of which tps features are available 0.144
And I shutdown Tails and wait for the computer to power off 4.083
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.073
After features/support/hooks.rb:331 0.520
After features/support/hooks.rb:100 0.007
Tags: @product
2:11.279
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.751
And I log in to a new session 12.371
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.791
And I plug USB drive "to_upgrade" 2.250
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.797
Then the running Tails is installed on USB drive "to_upgrade" 16.025
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 3.835
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.602
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.238
Then all tps features from the old Tails version are active 0.936
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 2.852
And the expected persistent files created with the old Tails version are present in the filesystem 1.174
And all persistent directories from the old Tails version have safe access rights 2.061
After features/support/hooks.rb:331 0.635
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:44.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.437
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.018
And Tor is ready 21.753
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.355
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.473
Given I shutdown Tails and wait for the computer to power off 20.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.240
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.115
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.117
# 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.220
When the network is plugged 0.015
And Tor is ready 23.056
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.371
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.926
Given I shutdown Tails and wait for the computer to power off 17.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.557
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.201
And the file system changes introduced in version 6.3~testoverlayfs are present 0.436
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.017
And Tor is ready 22.185
Then the Upgrader considers the system as up-to-date 0.216
# 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 5.012
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.512
After features/support/hooks.rb:331 1.191
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
26.047
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.594
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 17.768
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.372
After features/support/hooks.rb:331 0.989
After features/support/hooks.rb:100 0.000