Project Number Date
test_Tails_ISO_devel 4480 02 Jul 2026, 11:18

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.691 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:1.276
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.040
When I start Tails from USB drive "old" with network unplugged 43.534
Then the boot device has safe access rights 2.903
And Tails is running from USB drive "old" 0.215
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:339 1.312
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.840
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 52.144
Then Tails is running from USB drive "old" 0.289
And I create a persistent partition 24.654
And I take note of which tps features are available 4.094
Then a Tails persistence partition exists on USB drive "old" 0.533
And I shutdown Tails and wait for the computer to power off 8.076
After features/support/hooks.rb:339 0.476
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.443
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.591
Then Tails is running from USB drive "old" 0.217
And all tps features are active 4.859
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
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.008
And I take note of which tps features are available 3.915
And I shutdown Tails and wait for the computer to power off 7.938
# 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" 12.161
After features/support/hooks.rb:339 0.375
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.514
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 7.709
And I log in to a new session 11.716
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.661
And I plug USB drive "to_upgrade" 2.206
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.076
Then the running Tails is installed on USB drive "to_upgrade" 14.872
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 2.102
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.155
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.250
Then all tps features from the old Tails version are active 1.041
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.554
And the expected persistent files created with the old Tails version are present in the filesystem 1.148
And all persistent directories from the old Tails version have safe access rights 1.886
After features/support/hooks.rb:339 0.524
After features/support/hooks.rb:108 0.005
3:51.397
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.116
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.308
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.511
When the network is plugged 0.020
And Tor is ready 13.538
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.467
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.833
Given I shutdown Tails and wait for the computer to power off 6.897
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.162
Then Tails is running version 6.2~testoverlayfs 0.024
And all tps features are active 4.924
And the file system changes introduced in version 6.2~testoverlayfs are present 1.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.251
When the network is plugged 0.014
And Tor is ready 10.083
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.767
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.140
Given I shutdown Tails and wait for the computer to power off 8.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.129
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.579
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.017
And Tor is ready 10.821
Then the Upgrader considers the system as up-to-date 10.661
# 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.170
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.321
After features/support/hooks.rb:339 1.040
After features/support/hooks.rb:108 0.009
20.064
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.422
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 8.428
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.862
After features/support/hooks.rb:339 0.683
After features/support/hooks.rb:108 0.000