Project Number Date
test_Tails_ISO_web-release-7.14 3 29 Sep 2026, 18:21

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 12:3.839 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.808
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.125
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.400
When I start Tails from USB drive "old" with network unplugged 54.626
Then the boot device has safe access rights 2.062
And Tails is running from USB drive "old" 0.183
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 3.729
After features/support/hooks.rb:108 0.066
Tags: @product
1:25.520
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 51.040
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 23.556
And I take note of which tps features are available 7.034
Then a Tails persistence partition exists on USB drive "old" 0.625
And I shutdown Tails and wait for the computer to power off 2.952
After features/support/hooks.rb:339 0.362
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.245
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.035
Then Tails is running from USB drive "old" 0.206
And all tps features are active 7.296
When I write some files expected to persist 1.217
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.835
And I take note of which tps features are available 7.343
And I shutdown Tails and wait for the computer to power off 2.750
# 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.003
After features/support/hooks.rb:339 0.562
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.507
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.697
And I log in to a new session 12.412
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.100
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.546
Then the running Tails is installed on USB drive "to_upgrade" 20.239
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 3.764
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.754
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.645
Then all tps features from the old Tails version are active 1.073
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.625
And the expected persistent files created with the old Tails version are present in the filesystem 1.143
And all persistent directories from the old Tails version have safe access rights 1.953
After features/support/hooks.rb:339 1.031
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:55.846
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 23.752
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.252
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.033
And Tor is ready 13.520
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.945
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.036
Given I shutdown Tails and wait for the computer to power off 6.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.136
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.420
And the file system changes introduced in version 6.2~testoverlayfs are present 0.181
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.207
When the network is plugged 0.023
And Tor is ready 10.282
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.632
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.371
Given I shutdown Tails and wait for the computer to power off 4.002
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.941
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.617
And the file system changes introduced in version 6.3~testoverlayfs are present 0.424
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.031
And Tor is ready 10.680
Then the Upgrader considers the system as up-to-date 0.094
# 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.209
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 1.154
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.155
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.445
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.272
And Tor is ready 8.496
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.597
After features/support/hooks.rb:339 0.539
After features/support/hooks.rb:108 0.000