Project Number Date
test_Tails_ISO_stable 6129 09 Feb 2026, 18:19

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:2.366 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:41.360
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.017
And I write an old version of the Tails USB image to disk "old" 14.508
When I start Tails from USB drive "old" with network unplugged 1:21.811
Then the boot device has safe access rights 3.189
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 3.448
After features/support/hooks.rb:100 0.013
Tags: @product
1:25.771
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 55.366
Then Tails is running from USB drive "old" 0.272
And I create a persistent partition 24.543
And I take note of which tps features are available 0.709
Then a Tails persistence partition exists on USB drive "old" 0.570
And I shutdown Tails and wait for the computer to power off 4.227
After features/support/hooks.rb:331 0.147
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.406
Then Tails is running from USB drive "old" 0.242
And all tps features are active 1.201
When I write some files expected to persist 1.415
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 1.898
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 8.412
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.913
After features/support/hooks.rb:331 0.109
After features/support/hooks.rb:100 0.011
Tags: @product
2:19.610
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.179
And I log in to a new session 15.408
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.885
And I plug USB drive "to_upgrade" 2.482
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.332
Then the running Tails is installed on USB drive "to_upgrade" 16.996
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:331 4.068
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.518
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:2.701
Then all tps features from the old Tails version are active 1.015
And Tails is running from USB drive "to_upgrade" 0.243
And the boot device has safe access rights 2.535
And the expected persistent files created with the old Tails version are present in the filesystem 1.063
And all persistent directories from the old Tails version have safe access rights 1.882
After features/support/hooks.rb:331 0.758
After features/support/hooks.rb:100 0.007
4:9.012
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.201
And no SquashFS delta is installed 0.075
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.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.023
And Tor is ready 12.759
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.820
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.799
Given I shutdown Tails and wait for the computer to power off 9.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.970
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.148
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.194
When the network is plugged 0.014
And Tor is ready 9.674
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.376
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.937
Given I shutdown Tails and wait for the computer to power off 8.471
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.882
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.254
And the file system changes introduced in version 6.3~testoverlayfs are present 0.403
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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.021
And Tor is ready 39.954
Then the Upgrader considers the system as up-to-date 0.102
# 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.838
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.529
After features/support/hooks.rb:331 1.122
After features/support/hooks.rb:100 0.011
48.869
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.553
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 40.634
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.348
After features/support/hooks.rb:331 0.858
After features/support/hooks.rb:100 0.000