Project Number Date
test_Tails_ISO_devel 4669 10 Oct 2026, 11:06

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:10.750 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:9.033
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.096
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" 13.593
When I start Tails from USB drive "old" with network unplugged 51.466
Then the boot device has safe access rights 2.144
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.506
After features/support/hooks.rb:108 0.012
Tags: @product
1:21.734
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 46.787
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 23.448
And I take note of which tps features are available 6.510
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 4.168
After features/support/hooks.rb:339 0.568
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.893
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.305
Then Tails is running from USB drive "old" 0.203
And all tps features are active 7.269
When I write some files expected to persist 1.319
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.129
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 1.827
And I take note of which tps features are available 6.292
And I shutdown Tails and wait for the computer to power off 2.576
# 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.545
After features/support/hooks.rb:339 0.383
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.102
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.588
And I log in to a new session 12.093
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.606
And I plug USB drive "to_upgrade" 2.187
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.111
Then the running Tails is installed on USB drive "to_upgrade" 18.259
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 1.809
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.745
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.241
Then all tps features from the old Tails version are active 1.091
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 2.230
And the expected persistent files created with the old Tails version are present in the filesystem 1.003
And all persistent directories from the old Tails version have safe access rights 1.863
After features/support/hooks.rb:339 0.992
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:28.668
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 7.963
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.178
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.172
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.224
When the network is plugged 0.033
And Tor is ready 14.737
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.309
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.440
Given I shutdown Tails and wait for the computer to power off 5.655
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.440
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.487
And the file system changes introduced in version 6.2~testoverlayfs are present 0.182
And only the 6.2~testoverlayfs SquashFS delta is installed 0.033
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.179
When the network is plugged 0.022
And Tor is ready 10.342
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.312
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.765
Given I shutdown Tails and wait for the computer to power off 4.035
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.412
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.027
And the file system changes introduced in version 6.3~testoverlayfs are present 0.321
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.120
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.028
And Tor is ready 10.157
Then the Upgrader considers the system as up-to-date 0.111
# 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.249
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.261
After features/support/hooks.rb:339 0.652
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
18.573
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.010
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.052
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 9.317
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.884
After features/support/hooks.rb:339 0.616
After features/support/hooks.rb:108 0.000