Project Number Date
test_Tails_ISO_devel 4670 11 Oct 2026, 11:15

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:4.187 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:10.435
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.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.060
When I start Tails from USB drive "old" with network unplugged 54.005
Then the boot device has safe access rights 1.657
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.155
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.653
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.217
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 47.344
Then Tails is running from USB drive "old" 0.135
And I create a persistent partition 22.670
And I take note of which tps features are available 5.978
Then a Tails persistence partition exists on USB drive "old" 0.480
And I shutdown Tails and wait for the computer to power off 2.529
After features/support/hooks.rb:339 0.604
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.166
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.225
Then Tails is running from USB drive "old" 0.158
And all tps features are active 6.648
When I write some files expected to persist 1.007
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.110
And all persistence configuration files have safe access rights 0.260
And all persistent directories from the old Tails version have safe access rights 1.607
And I take note of which tps features are available 5.935
And I shutdown Tails and wait for the computer to power off 3.921
# 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.207
After features/support/hooks.rb:339 0.169
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.195
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.292
And I log in to a new session 10.293
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.630
And I plug USB drive "to_upgrade" 2.761
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.119
Then the running Tails is installed on USB drive "to_upgrade" 17.877
And I unplug USB drive "to_upgrade" 0.109
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 0.667
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.276
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.727
Then all tps features from the old Tails version are active 1.014
And Tails is running from USB drive "to_upgrade" 0.205
And the boot device has safe access rights 1.951
And the expected persistent files created with the old Tails version are present in the filesystem 0.850
And all persistent directories from the old Tails version have safe access rights 1.454
After features/support/hooks.rb:339 0.884
After features/support/hooks.rb:108 0.005
3:18.753
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.227
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
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.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.311
When the network is plugged 0.035
And Tor is ready 12.856
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.389
Given I shutdown Tails and wait for the computer to power off 5.241
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.390
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.064
And the file system changes introduced in version 6.2~testoverlayfs are present 0.178
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.112
# 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.182
When the network is plugged 0.033
And Tor is ready 10.238
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.299
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.344
Given I shutdown Tails and wait for the computer to power off 2.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.052
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.137
And the file system changes introduced in version 6.3~testoverlayfs are present 0.301
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.045
And Tor is ready 9.997
Then the Upgrader considers the system as up-to-date 0.105
# 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.129
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.305
After features/support/hooks.rb:339 0.517
After features/support/hooks.rb:108 0.021
32.142
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 20.846
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 10.726
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.285
After features/support/hooks.rb:339 0.533
After features/support/hooks.rb:108 0.000