Project Number Date
test_Tails_ISO_devel 4217 07 Feb 2026, 11:52

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:17.348 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:13.564
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.610
When I start Tails from USB drive "old" with network unplugged 54.353
Then the boot device has safe access rights 2.780
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.244
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 1.303
After features/support/hooks.rb:100 0.007
Tags: @product
1:36.959
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 58.089
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 28.044
And I take note of which tps features are available 1.175
Then a Tails persistence partition exists on USB drive "old" 0.728
And I shutdown Tails and wait for the computer to power off 8.606
After features/support/hooks.rb:331 0.457
After features/support/hooks.rb:100 0.007
Tags: @product
1:34.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.477
Then Tails is running from USB drive "old" 0.263
And all tps features are active 1.311
When I write some files expected to persist 1.577
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.363
And all persistence configuration files have safe access rights 0.517
And all persistent directories from the old Tails version have safe access rights 2.586
And I take note of which tps features are available 0.195
And I shutdown Tails and wait for the computer to power off 8.304
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.136
After features/support/hooks.rb:331 0.619
After features/support/hooks.rb:100 0.020
Tags: @product
2:16.740
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 without a persistent partition and stopped at Tails Greeter's login screen 8.857
And I log in to a new session 12.487
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.250
And I plug USB drive "to_upgrade" 2.264
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.977
Then the running Tails is installed on USB drive "to_upgrade" 17.616
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 3.398
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.600
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.306
Then all tps features from the old Tails version are active 1.093
And Tails is running from USB drive "to_upgrade" 0.300
And the boot device has safe access rights 3.023
And the expected persistent files created with the old Tails version are present in the filesystem 1.489
And all persistent directories from the old Tails version have safe access rights 2.294
After features/support/hooks.rb:331 0.691
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
3:54.636
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 8.641
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.017
And Tor is ready 13.956
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.013
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.538
Given I shutdown Tails and wait for the computer to power off 7.139
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.441
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.162
And the file system changes introduced in version 6.2~testoverlayfs are present 0.258
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.239
When the network is plugged 0.016
And Tor is ready 10.414
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.966
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.697
Given I shutdown Tails and wait for the computer to power off 8.102
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.723
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.144
And the file system changes introduced in version 6.3~testoverlayfs are present 0.383
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.016
And Tor is ready 11.359
Then the Upgrader considers the system as up-to-date 10.644
# 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.776
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:331 1.046
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
23.053
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.387
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 11.927
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.323
After features/support/hooks.rb:331 1.009
After features/support/hooks.rb:100 0.000