Project Number Date
test_Tails_ISO_devel 4170 15 Jan 2026, 17:33

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:47.708 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:12.636
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.180
When I start Tails from USB drive "old" with network unplugged 53.524
Then the boot device has safe access rights 3.058
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.469
After features/support/hooks.rb:100 0.025
Tags: @product
1:27.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 53.412
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 24.434
And I take note of which tps features are available 0.796
Then a Tails persistence partition exists on USB drive "old" 0.533
And I shutdown Tails and wait for the computer to power off 7.841
After features/support/hooks.rb:331 0.552
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.348
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.576
Then Tails is running from USB drive "old" 0.256
And all tps features are active 1.488
When I write some files expected to persist 1.240
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.378
And all persistent directories from the old Tails version have safe access rights 2.203
And I take note of which tps features are available 0.181
And I shutdown Tails and wait for the computer to power off 8.285
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.521
After features/support/hooks.rb:331 0.480
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.269
And I log in to a new session 11.575
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.012
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.231
Then the running Tails is installed on USB drive "to_upgrade" 15.919
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 3.588
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.715
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.128
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.841
Then all tps features from the old Tails version are active 1.055
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 2.528
And the expected persistent files created with the old Tails version are present in the filesystem 1.038
And all persistent directories from the old Tails version have safe access rights 1.840
After features/support/hooks.rb:331 0.576
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:56.613
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.373
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.286
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.015
And Tor is ready 12.553
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.124
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.934
Given I shutdown Tails and wait for the computer to power off 6.982
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.602
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.210
And the file system changes introduced in version 6.2~testoverlayfs are present 0.216
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.197
When the network is plugged 0.020
And Tor is ready 11.774
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.138
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.954
Given I shutdown Tails and wait for the computer to power off 8.045
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.417
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.228
And the file system changes introduced in version 6.3~testoverlayfs are present 0.440
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.015
And Tor is ready 39.667
Then the Upgrader considers the system as up-to-date 0.097
# 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.511
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.426
After features/support/hooks.rb:331 0.716
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
19.506
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.569
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
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.043
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.555
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.077
After features/support/hooks.rb:331 0.701
After features/support/hooks.rb:100 0.000