Project Number Date
test_Tails_ISO_devel 4236 17 Feb 2026, 14:24

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 16:47.278 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:32.920
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.217
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 31.094
When I start Tails from USB drive "old" with network unplugged 55.899
Then the boot device has safe access rights 3.549
And Tails is running from USB drive "old" 0.404
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.228
After features/support/hooks.rb:331 1.449
After features/support/hooks.rb:100 0.014
Tags: @product
1:47.068
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.280
And I start Tails from USB drive "old" with network unplugged and I login 1:7.929
Then Tails is running from USB drive "old" 0.294
And I create a persistent partition 31.282
And I take note of which tps features are available 1.556
Then a Tails persistence partition exists on USB drive "old" 0.727
And I shutdown Tails and wait for the computer to power off 4.997
After features/support/hooks.rb:331 0.574
After features/support/hooks.rb:100 0.011
Tags: @product
1:57.847
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.328
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:21.808
Then Tails is running from USB drive "old" 0.517
And all tps features are active 2.281
When I write some files expected to persist 1.951
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.201
And all persistence configuration files have safe access rights 0.439
And all persistent directories from the old Tails version have safe access rights 2.405
And I take note of which tps features are available 0.541
And I shutdown Tails and wait for the computer to power off 7.984
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.388
After features/support/hooks.rb:331 0.205
After features/support/hooks.rb:100 0.012
Tags: @product
2:32.447
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 10.818
And I log in to a new session 10.876
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.441
And I plug USB drive "to_upgrade" 2.668
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.244
Then the running Tails is installed on USB drive "to_upgrade" 22.942
And I unplug USB drive "to_upgrade" 0.237
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:331 3.718
After features/support/hooks.rb:100 0.000
Tags: @product
1:33.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:23.188
Then all tps features from the old Tails version are active 1.531
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 4.186
And the expected persistent files created with the old Tails version are present in the filesystem 1.676
And all persistent directories from the old Tails version have safe access rights 2.664
After features/support/hooks.rb:331 0.813
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:0.409
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 10.218
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.347
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.052
And Tor is ready 43.562
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:4.627
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.727
Given I shutdown Tails and wait for the computer to power off 8.615
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.494
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.597
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.152
# 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.290
When the network is plugged 0.068
And Tor is ready 13.425
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.729
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.562
Given I shutdown Tails and wait for the computer to power off 7.808
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.784
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 2.392
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.324
When the network is plugged 0.142
And Tor is ready 12.452
Then the Upgrader considers the system as up-to-date 0.116
# 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 7.361
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.125
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
22.826
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 with a persistent partition enabled and logged in 10.006
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 11.750
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.590
After features/support/hooks.rb:331 1.069
After features/support/hooks.rb:100 0.000