Project Number Date
test_Tails_ISO_stable 6232 25 Mar 2026, 13:22

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:10.341 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.418
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 15.022
When I start Tails from USB drive "old" with network unplugged 58.213
Then the boot device has safe access rights 3.202
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:331 3.915
After features/support/hooks.rb:100 0.007
Tags: @product
1:31.898
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 57.031
Then Tails is running from USB drive "old" 0.266
And I create a persistent partition 26.162
And I take note of which tps features are available 0.698
Then a Tails persistence partition exists on USB drive "old" 0.534
And I shutdown Tails and wait for the computer to power off 7.108
After features/support/hooks.rb:331 0.519
After features/support/hooks.rb:100 0.008
Tags: @product
1:33.988
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.181
Then Tails is running from USB drive "old" 0.257
And all tps features are active 1.119
When I write some files expected to persist 1.310
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.459
And all persistent directories from the old Tails version have safe access rights 2.017
And I take note of which tps features are available 0.181
And I shutdown Tails and wait for the computer to power off 8.466
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.731
After features/support/hooks.rb:331 0.336
After features/support/hooks.rb:100 0.009
Tags: @product
2:16.713
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.983
And I log in to a new session 14.447
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.919
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.497
Then the running Tails is installed on USB drive "to_upgrade" 17.310
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:331 2.684
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.340
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.639
Then all tps features from the old Tails version are active 1.163
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.860
And the expected persistent files created with the old Tails version are present in the filesystem 1.287
And all persistent directories from the old Tails version have safe access rights 2.028
After features/support/hooks.rb:331 1.050
After features/support/hooks.rb:100 0.028
4:47.067
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.994
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.045
And Tor is ready 22.873
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.674
Given I shutdown Tails and wait for the computer to power off 14.850
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.421
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 1.249
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
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.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.211
When the network is plugged 0.024
And Tor is ready 21.919
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.406
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.888
Given I shutdown Tails and wait for the computer to power off 12.589
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.804
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.214
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.019
And Tor is ready 23.582
Then the Upgrader considers the system as up-to-date 0.154
# 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.976
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.452
After features/support/hooks.rb:331 1.082
After features/support/hooks.rb:100 0.046
27.915
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.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 18.949
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.468
After features/support/hooks.rb:331 0.876
After features/support/hooks.rb:100 0.000