Project Number Date
test_Tails_ISO_stable 6099 28 Jan 2026, 22:33

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:34.768 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
2:8.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.356
When I start Tails from USB drive "old" with network unplugged 1:49.652
Then the boot device has safe access rights 2.946
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 3.507
After features/support/hooks.rb:100 0.007
Tags: @product
1:46.193
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 1:11.608
Then Tails is running from USB drive "old" 0.405
And I create a persistent partition 24.479
And I take note of which tps features are available 0.851
Then a Tails persistence partition exists on USB drive "old" 0.621
And I shutdown Tails and wait for the computer to power off 8.166
After features/support/hooks.rb:331 0.501
After features/support/hooks.rb:100 0.031
Tags: @product
1:36.865
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.935
Then Tails is running from USB drive "old" 0.294
And all tps features are active 1.355
When I write some files expected to persist 1.192
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.310
And all persistent directories from the old Tails version have safe access rights 1.860
And I take note of which tps features are available 0.181
And I shutdown Tails and wait for the computer to power off 6.969
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.526
After features/support/hooks.rb:331 0.559
After features/support/hooks.rb:100 0.006
Tags: @product
2:29.995
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 21.758
And I log in to a new session 13.310
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.736
And I plug USB drive "to_upgrade" 2.287
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.852
Then the running Tails is installed on USB drive "to_upgrade" 17.739
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.159
After features/support/hooks.rb:331 3.764
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.490
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.876
Then all tps features from the old Tails version are active 1.043
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.839
And the expected persistent files created with the old Tails version are present in the filesystem 1.284
And all persistent directories from the old Tails version have safe access rights 2.088
After features/support/hooks.rb:331 0.881
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:54.705
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.455
And no SquashFS delta is installed 0.199
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.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.346
When the network is plugged 0.043
And Tor is ready 14.167
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.435
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.472
Given I shutdown Tails and wait for the computer to power off 14.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.518
Then Tails is running version 6.2~testoverlayfs 0.028
And all tps features are active 1.517
And the file system changes introduced in version 6.2~testoverlayfs are present 0.267
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.195
When the network is plugged 0.016
And Tor is ready 9.843
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.119
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.363
Given I shutdown Tails and wait for the computer to power off 8.687
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.332
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.042
And the file system changes introduced in version 6.3~testoverlayfs are present 0.358
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.016
And Tor is ready 12.226
Then the Upgrader considers the system as up-to-date 10.568
# 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.218
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.772
After features/support/hooks.rb:331 0.766
After features/support/hooks.rb:100 0.033
Tags: @product @automatic_upgrade
21.703
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.975
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.468
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.934
After features/support/hooks.rb:331 1.035
After features/support/hooks.rb:100 0.000