Project Number Date
test_Tails_ISO_stable 6167 24 Feb 2026, 22:41

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:36.826 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:38.646
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.410
When I start Tails from USB drive "old" with network unplugged 1:19.305
Then the boot device has safe access rights 3.057
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 1.456
After features/support/hooks.rb:100 0.007
Tags: @product
1:34.829
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 1:0.492
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 25.776
And I take note of which tps features are available 0.737
Then a Tails persistence partition exists on USB drive "old" 0.600
And I shutdown Tails and wait for the computer to power off 6.893
After features/support/hooks.rb:331 0.591
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.768
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.325
Then Tails is running from USB drive "old" 0.308
And all tps features are active 1.155
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.163
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 1.971
And I take note of which tps features are available 0.186
And I shutdown Tails and wait for the computer to power off 4.197
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.809
After features/support/hooks.rb:331 0.538
After features/support/hooks.rb:100 0.008
Tags: @product
2:27.029
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 without a persistent partition and stopped at Tails Greeter's login screen 8.433
And I log in to a new session 14.240
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.787
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.595
Then the running Tails is installed on USB drive "to_upgrade" 16.454
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 1.244
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.291
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.617
Then all tps features from the old Tails version are active 1.026
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.445
And the expected persistent files created with the old Tails version are present in the filesystem 1.124
And all persistent directories from the old Tails version have safe access rights 1.767
After features/support/hooks.rb:331 1.099
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:48.238
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.611
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.327
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.016
And Tor is ready 26.658
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.389
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.380
Given I shutdown Tails and wait for the computer to power off 19.697
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.878
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.117
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.206
When the network is plugged 0.022
And Tor is ready 22.090
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.672
Given I shutdown Tails and wait for the computer to power off 17.521
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.809
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.237
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.017
And Tor is ready 22.138
Then the Upgrader considers the system as up-to-date 0.109
# 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.423
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.509
After features/support/hooks.rb:331 0.931
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
28.022
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.681
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.366
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 19.506
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.370
After features/support/hooks.rb:331 0.719
After features/support/hooks.rb:100 0.000