Project Number Date
test_Tails_ISO_migrate-vms 1 07 Oct 2026, 00:25

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:36.526 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:15.242
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.174
When I start Tails from USB drive "old" with network unplugged 56.255
Then the boot device has safe access rights 3.046
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 1.118
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.214
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login 48.836
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 24.886
And I take note of which tps features are available 6.456
Then a Tails persistence partition exists on USB drive "old" 0.538
And I shutdown Tails and wait for the computer to power off 4.150
After features/support/hooks.rb:339 0.626
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.782
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.300
Then Tails is running from USB drive "old" 0.194
And all tps features are active 7.695
When I write some files expected to persist 1.180
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.275
And all persistent directories from the old Tails version have safe access rights 1.696
And I take note of which tps features are available 6.229
And I shutdown Tails and wait for the computer to power off 7.731
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.188
After features/support/hooks.rb:339 0.485
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.929
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.592
And I log in to a new session 12.015
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.646
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.798
Then the running Tails is installed on USB drive "to_upgrade" 17.377
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.777
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.854
Then all tps features from the old Tails version are active 1.086
And Tails is running from USB drive "to_upgrade" 0.206
And the boot device has safe access rights 2.067
And the expected persistent files created with the old Tails version are present in the filesystem 0.887
And all persistent directories from the old Tails version have safe access rights 1.575
After features/support/hooks.rb:339 0.424
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
3:39.591
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.407
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.422
When the network is plugged 0.031
And Tor is ready 12.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.031
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.818
Given I shutdown Tails and wait for the computer to power off 5.323
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.199
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.990
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.162
When the network is plugged 0.024
And Tor is ready 10.293
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.295
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.484
Given I shutdown Tails and wait for the computer to power off 4.130
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.329
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.307
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.091
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.024
And Tor is ready 10.354
Then the Upgrader considers the system as up-to-date 10.490
# 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 3.213
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.338
After features/support/hooks.rb:339 0.801
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.013
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.205
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.489
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.930
After features/support/hooks.rb:339 0.668
After features/support/hooks.rb:108 0.000