Project Number Date
test_Tails_ISO_devel 4212 05 Feb 2026, 11:56

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 11:59.424 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:10.028
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.150
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.396
When I start Tails from USB drive "old" with network unplugged 50.950
Then the boot device has safe access rights 2.646
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:331 3.588
After features/support/hooks.rb:100 0.032
Tags: @product
1:31.269
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 57.932
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 27.090
And I take note of which tps features are available 0.827
Then a Tails persistence partition exists on USB drive "old" 0.723
And I shutdown Tails and wait for the computer to power off 4.342
After features/support/hooks.rb:331 0.596
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.637
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.623
Then Tails is running from USB drive "old" 0.273
And all tps features are active 1.235
When I write some files expected to persist 1.690
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.298
And I take note of which tps features are available 0.228
And I shutdown Tails and wait for the computer to power off 4.211
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.379
After features/support/hooks.rb:331 0.234
After features/support/hooks.rb:100 0.026
Tags: @product
2:15.820
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.882
And I log in to a new session 12.162
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.023
And I plug USB drive "to_upgrade" 2.298
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.364
Then the running Tails is installed on USB drive "to_upgrade" 16.802
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 2.348
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.110
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.394
Then all tps features from the old Tails version are active 1.126
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.603
And the expected persistent files created with the old Tails version are present in the filesystem 1.196
And all persistent directories from the old Tails version have safe access rights 2.159
After features/support/hooks.rb:331 0.985
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
3:53.780
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 with a persistent partition enabled and logged in 9.587
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.428
When the network is plugged 0.026
And Tor is ready 13.427
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.996
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.670
Given I shutdown Tails and wait for the computer to power off 5.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.131
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 1.444
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.211
# 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.329
When the network is plugged 0.022
And Tor is ready 10.233
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.205
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.213
Given I shutdown Tails and wait for the computer to power off 7.963
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.376
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.530
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.195
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.021
And Tor is ready 11.383
Then the Upgrader considers the system as up-to-date 10.740
# 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.958
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.357
After features/support/hooks.rb:331 0.717
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
21.028
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.148
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.102
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.999
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.342
After features/support/hooks.rb:331 0.720
After features/support/hooks.rb:100 0.000