Project Number Date
test_Tails_ISO_devel 4350 18 Apr 2026, 11:24

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:55.531 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:18.291
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.237
When I start Tails from USB drive "old" with network unplugged 59.340
Then the boot device has safe access rights 2.874
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.158
After features/support/hooks.rb:331 1.419
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.039
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 55.939
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 24.965
And I take note of which tps features are available 0.786
Then a Tails persistence partition exists on USB drive "old" 0.573
And I shutdown Tails and wait for the computer to power off 8.457
After features/support/hooks.rb:331 0.391
After features/support/hooks.rb:100 0.008
Tags: @product
1:30.416
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.185
Then Tails is running from USB drive "old" 0.292
And all tps features are active 1.198
When I write some files expected to persist 1.351
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.224
And all persistence configuration files have safe access rights 0.495
And all persistent directories from the old Tails version have safe access rights 1.997
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 8.410
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.009
After features/support/hooks.rb:331 0.473
After features/support/hooks.rb:100 0.009
Tags: @product
2:21.622
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.402
And I log in to a new session 18.431
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.794
And I plug USB drive "to_upgrade" 2.260
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.118
Then the running Tails is installed on USB drive "to_upgrade" 17.280
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.155
After features/support/hooks.rb:331 2.604
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.001
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.345
Then all tps features from the old Tails version are active 1.029
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.861
And the expected persistent files created with the old Tails version are present in the filesystem 1.192
And all persistent directories from the old Tails version have safe access rights 2.284
After features/support/hooks.rb:331 0.881
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:30.069
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.883
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.400
When the network is plugged 0.021
And Tor is ready 26.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.678
Given I shutdown Tails and wait for the computer to power off 21.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.550
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.225
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.239
When the network is plugged 0.013
And Tor is ready 22.073
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.410
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.478
Given I shutdown Tails and wait for the computer to power off 12.148
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.417
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.467
And the file system changes introduced in version 6.3~testoverlayfs are present 0.367
And only the 6.3~testoverlayfs SquashFS delta is installed 0.075
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.293
When the network is plugged 0.022
And Tor is ready 22.029
Then the Upgrader considers the system as up-to-date 0.105
# 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.703
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:331 1.035
After features/support/hooks.rb:100 0.051
Tags: @product @automatic_upgrade
28.091
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.012
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 19.254
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
After features/support/hooks.rb:331 1.008
After features/support/hooks.rb:100 0.000