Project Number Date
test_Tails_ISO_devel 4271 10 Mar 2026, 11:17

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:50.121 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:12.837
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 14.244
When I start Tails from USB drive "old" with network unplugged 53.739
Then the boot device has safe access rights 2.868
And Tails is running from USB drive "old" 0.270
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 1.386
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.466
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 57.838
Then Tails is running from USB drive "old" 0.246
And I create a persistent partition 26.448
And I take note of which tps features are available 0.734
Then a Tails persistence partition exists on USB drive "old" 0.599
And I shutdown Tails and wait for the computer to power off 7.526
After features/support/hooks.rb:331 0.385
After features/support/hooks.rb:100 0.008
Tags: @product
1:39.722
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.885
Then Tails is running from USB drive "old" 0.393
And all tps features are active 1.519
When I write some files expected to persist 1.802
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.336
And all persistence configuration files have safe access rights 0.591
And all persistent directories from the old Tails version have safe access rights 2.818
And I take note of which tps features are available 0.179
And I shutdown Tails and wait for the computer to power off 8.842
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.287
After features/support/hooks.rb:331 0.251
After features/support/hooks.rb:100 0.012
Tags: @product
2:16.982
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 without a persistent partition and stopped at Tails Greeter's login screen 9.047
And I log in to a new session 11.981
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.889
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.700
Then the running Tails is installed on USB drive "to_upgrade" 18.733
And I unplug USB drive "to_upgrade" 0.222
And I unplug USB drive "__internal" 0.164
After features/support/hooks.rb:331 2.463
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.485
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.116
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.133
Then all tps features from the old Tails version are active 1.025
And Tails is running from USB drive "to_upgrade" 0.489
And the boot device has safe access rights 3.851
And the expected persistent files created with the old Tails version are present in the filesystem 1.435
And all persistent directories from the old Tails version have safe access rights 2.432
After features/support/hooks.rb:331 0.947
After features/support/hooks.rb:100 0.028
5:18.101
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.756
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
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.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.016
And Tor is ready 21.878
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.657
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.990
Given I shutdown Tails and wait for the computer to power off 16.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.175
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.743
And the file system changes introduced in version 6.2~testoverlayfs are present 0.463
And only the 6.2~testoverlayfs SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.271
When the network is plugged 0.054
And Tor is ready 41.417
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.432
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.325
Given I shutdown Tails and wait for the computer to power off 17.977
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.240
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.278
And the file system changes introduced in version 6.3~testoverlayfs are present 0.436
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.013
And Tor is ready 22.989
Then the Upgrader considers the system as up-to-date 0.132
# 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.815
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.542
After features/support/hooks.rb:331 0.918
After features/support/hooks.rb:100 0.014
28.525
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.975
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.080
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.020
And Tor is ready 18.771
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.397
After features/support/hooks.rb:331 1.002
After features/support/hooks.rb:100 0.000