Project Number Date
test_Tails_ISO_migrate-vms 2 07 Oct 2026, 01:40

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.195 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:7.005
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.111
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.328
When I start Tails from USB drive "old" with network unplugged 49.883
Then the boot device has safe access rights 2.077
And Tails is running from USB drive "old" 0.199
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.154
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.531
After features/support/hooks.rb:108 0.044
Tags: @product
1:24.172
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login 49.403
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 23.173
And I take note of which tps features are available 6.603
Then a Tails persistence partition exists on USB drive "old" 0.644
And I shutdown Tails and wait for the computer to power off 3.977
After features/support/hooks.rb:339 0.161
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.998
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.694
Then Tails is running from USB drive "old" 0.275
And all tps features are active 7.685
When I write some files expected to persist 1.092
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.271
And all persistent directories from the old Tails version have safe access rights 1.552
And I take note of which tps features are available 6.555
And I shutdown Tails and wait for the computer to power off 4.069
# 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.542
After features/support/hooks.rb:339 0.305
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.730
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.331
And I log in to a new session 11.879
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.720
And I plug USB drive "to_upgrade" 2.201
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.193
Then the running Tails is installed on USB drive "to_upgrade" 18.151
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.726
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.665
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.786
Then all tps features from the old Tails version are active 0.974
And Tails is running from USB drive "to_upgrade" 0.190
And the boot device has safe access rights 2.163
And the expected persistent files created with the old Tails version are present in the filesystem 0.865
And all persistent directories from the old Tails version have safe access rights 1.605
After features/support/hooks.rb:339 0.509
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
4:2.719
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 21.259
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.173
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.270
When the network is plugged 0.589
And Tor is ready 12.791
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 4.683
Given I shutdown Tails and wait for the computer to power off 5.372
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.892
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.269
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.154
When the network is plugged 0.030
And Tor is ready 19.799
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.321
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.071
Given I shutdown Tails and wait for the computer to power off 4.120
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.261
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.415
And the file system changes introduced in version 6.3~testoverlayfs are present 0.267
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.173
When the network is plugged 0.041
And Tor is ready 10.379
Then the Upgrader considers the system as up-to-date 10.418
# 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.695
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
18.902
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 7.785
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.185
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.760
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.046
After features/support/hooks.rb:339 0.820
After features/support/hooks.rb:108 0.000