Project Number Date
test_Tails_ISO_stable 6130 09 Feb 2026, 18: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 12:50.033 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:20.543
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 25.988
When I start Tails from USB drive "old" with network unplugged 49.506
Then the boot device has safe access rights 2.978
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.233
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:331 3.679
After features/support/hooks.rb:100 0.010
Tags: @product
1:35.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login 1:0.387
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 28.395
And I take note of which tps features are available 1.075
Then a Tails persistence partition exists on USB drive "old" 0.675
And I shutdown Tails and wait for the computer to power off 4.887
After features/support/hooks.rb:331 0.655
After features/support/hooks.rb:100 0.010
Tags: @product
1:42.726
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.700
Then Tails is running from USB drive "old" 0.313
And all tps features are active 1.861
When I write some files expected to persist 1.497
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.088
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 7.425
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.658
After features/support/hooks.rb:331 0.136
After features/support/hooks.rb:100 0.010
Tags: @product
2:16.785
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.866
And I log in to a new session 9.437
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.125
And I plug USB drive "to_upgrade" 3.182
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.059
Then the running Tails is installed on USB drive "to_upgrade" 18.733
And I unplug USB drive "to_upgrade" 0.179
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:331 1.851
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.952
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.657
Then all tps features from the old Tails version are active 1.449
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 2.815
And the expected persistent files created with the old Tails version are present in the filesystem 1.370
And all persistent directories from the old Tails version have safe access rights 2.189
After features/support/hooks.rb:331 0.822
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:12.253
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.414
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.389
When the network is plugged 0.059
And Tor is ready 12.232
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.707
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.368
Given I shutdown Tails and wait for the computer to power off 7.951
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.061
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.142
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.187
# 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.258
When the network is plugged 0.066
And Tor is ready 11.991
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.151
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.279
Given I shutdown Tails and wait for the computer to power off 7.706
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.023
Then Tails is running version 6.3~testoverlayfs 0.194
And all tps features are active 2.552
And the file system changes introduced in version 6.3~testoverlayfs are present 0.422
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.090
And Tor is ready 13.041
Then the Upgrader considers the system as up-to-date 0.162
# 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.593
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.694
After features/support/hooks.rb:331 1.039
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
21.911
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.446
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.048
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.090
And Tor is ready 11.374
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.659
After features/support/hooks.rb:331 1.010
After features/support/hooks.rb:100 0.000