Project Number Date
test_Tails_ISO_devel 4334 11 Apr 2026, 08:02

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 12:59.632 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:6.691
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.362
When I start Tails from USB drive "old" with network unplugged 49.271
Then the boot device has safe access rights 2.343
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.480
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.008
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 51.441
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 23.681
And I take note of which tps features are available 0.681
Then a Tails persistence partition exists on USB drive "old" 0.556
And I shutdown Tails and wait for the computer to power off 8.359
After features/support/hooks.rb:331 0.410
After features/support/hooks.rb:100 0.008
Tags: @product
1:26.731
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.171
Then Tails is running from USB drive "old" 0.270
And all tps features are active 1.135
When I write some files expected to persist 1.307
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.147
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 1.826
And I take note of which tps features are available 0.162
And I shutdown Tails and wait for the computer to power off 7.866
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.357
After features/support/hooks.rb:331 0.098
After features/support/hooks.rb:100 0.008
Tags: @product
2:24.311
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.808
And I log in to a new session 17.478
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.694
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.066
Then the running Tails is installed on USB drive "to_upgrade" 15.771
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 0.625
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.418
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.641
Then all tps features from the old Tails version are active 0.998
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.519
And the expected persistent files created with the old Tails version are present in the filesystem 1.108
And all persistent directories from the old Tails version have safe access rights 1.863
After features/support/hooks.rb:331 0.831
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
4:58.963
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.333
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.562
When the network is plugged 0.016
And Tor is ready 28.059
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.741
Given I shutdown Tails and wait for the computer to power off 20.767
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.715
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.026
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.117
# 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.205
When the network is plugged 0.015
And Tor is ready 40.958
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.462
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.902
Given I shutdown Tails and wait for the computer to power off 17.207
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.934
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.178
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.048
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.049
And Tor is ready 20.845
Then the Upgrader considers the system as up-to-date 0.113
# 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.341
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.353
After features/support/hooks.rb:331 0.693
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
28.506
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.506
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.455
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 20.068
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.363
After features/support/hooks.rb:331 0.687
After features/support/hooks.rb:100 0.000