Project Number Date
test_Tails_ISO_devel 4238 17 Feb 2026, 15:06

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:48.488 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:4.573
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.270
When I start Tails from USB drive "old" with network unplugged 45.039
Then the boot device has safe access rights 3.208
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.222
After features/support/hooks.rb:331 1.512
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.766
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 55.210
Then Tails is running from USB drive "old" 0.609
And I create a persistent partition 25.993
And I take note of which tps features are available 0.866
Then a Tails persistence partition exists on USB drive "old" 0.638
And I shutdown Tails and wait for the computer to power off 8.395
After features/support/hooks.rb:331 0.633
After features/support/hooks.rb:100 0.008
Tags: @product
1:30.648
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.287
Then Tails is running from USB drive "old" 0.283
And all tps features are active 1.206
When I write some files expected to persist 1.376
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 2.135
And I take note of which tps features are available 0.251
And I shutdown Tails and wait for the computer to power off 8.048
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.493
After features/support/hooks.rb:331 0.191
After features/support/hooks.rb:100 0.018
Tags: @product
2:17.742
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 9.143
And I log in to a new session 13.122
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.867
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.255
Then the running Tails is installed on USB drive "to_upgrade" 17.724
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 2.647
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.591
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.096
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.038
Then all tps features from the old Tails version are active 1.112
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 3.306
And the expected persistent files created with the old Tails version are present in the filesystem 1.449
And all persistent directories from the old Tails version have safe access rights 2.294
After features/support/hooks.rb:331 0.751
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
3:45.283
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.674
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.419
When the network is plugged 0.014
And Tor is ready 13.271
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.563
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.142
Given I shutdown Tails and wait for the computer to power off 9.984
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.687
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.296
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.202
When the network is plugged 0.015
And Tor is ready 12.183
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.898
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.229
Given I shutdown Tails and wait for the computer to power off 4.204
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.240
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.351
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.178
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.284
When the network is plugged 0.021
And Tor is ready 11.084
Then the Upgrader considers the system as up-to-date 10.570
# 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.734
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.442
After features/support/hooks.rb:331 0.652
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
20.883
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 7.734
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
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.066
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.234
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.441
After features/support/hooks.rb:331 0.905
After features/support/hooks.rb:100 0.000