Project Number Date
test_Tails_ISO_devel 4169 15 Jan 2026, 15:49

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:49.534 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:24.415
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.228
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 26.796
When I start Tails from USB drive "old" with network unplugged 52.188
Then the boot device has safe access rights 3.266
And Tails is running from USB drive "old" 0.335
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:331 3.890
After features/support/hooks.rb:100 0.009
Tags: @product
1:38.930
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 1:0.308
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 28.665
And I take note of which tps features are available 1.253
Then a Tails persistence partition exists on USB drive "old" 0.646
And I shutdown Tails and wait for the computer to power off 7.593
After features/support/hooks.rb:331 0.634
After features/support/hooks.rb:100 0.010
Tags: @product
1:44.096
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.854
Then Tails is running from USB drive "old" 0.307
And all tps features are active 1.945
When I write some files expected to persist 1.522
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 2.242
And I take note of which tps features are available 0.429
And I shutdown Tails and wait for the computer to power off 7.472
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.617
After features/support/hooks.rb:331 0.299
After features/support/hooks.rb:100 0.009
Tags: @product
2:20.812
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 without a persistent partition and stopped at Tails Greeter's login screen 9.506
And I log in to a new session 9.871
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.127
And I plug USB drive "to_upgrade" 2.364
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.294
Then the running Tails is installed on USB drive "to_upgrade" 19.278
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:331 3.909
After features/support/hooks.rb:100 0.000
Tags: @product
1:22.651
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.297
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.139
Then all tps features from the old Tails version are active 1.388
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 3.000
And the expected persistent files created with the old Tails version are present in the filesystem 1.304
And all persistent directories from the old Tails version have safe access rights 2.237
After features/support/hooks.rb:331 0.849
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
3:57.516
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 9.905
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.204
And Tor is ready 12.594
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.831
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.615
Given I shutdown Tails and wait for the computer to power off 7.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.835
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 1.982
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.254
When the network is plugged 0.089
And Tor is ready 12.361
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.557
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.468
Given I shutdown Tails and wait for the computer to power off 3.261
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.617
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.175
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.064
And Tor is ready 12.062
Then the Upgrader considers the system as up-to-date 0.134
# 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 6.014
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.556
After features/support/hooks.rb:331 1.141
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
21.111
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 9.725
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.089
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 10.237
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.675
After features/support/hooks.rb:331 0.836
After features/support/hooks.rb:100 0.000