Project Number Date
test_Tails_ISO_web-release-7.14 5 29 Sep 2026, 22:09

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:35.056 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:6.482
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
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.963
When I start Tails from USB drive "old" with network unplugged 47.546
Then the boot device has safe access rights 3.128
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.084
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 1.412
After features/support/hooks.rb:108 0.013
Tags: @product
1:28.504
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 50.027
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 25.838
And I take note of which tps features are available 7.470
Then a Tails persistence partition exists on USB drive "old" 0.616
And I shutdown Tails and wait for the computer to power off 4.166
After features/support/hooks.rb:339 0.338
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.439
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.935
Then Tails is running from USB drive "old" 0.177
And all tps features are active 8.747
When I write some files expected to persist 1.266
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.318
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.447
And I shutdown Tails and wait for the computer to power off 4.124
# 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.552
After features/support/hooks.rb:339 0.366
After features/support/hooks.rb:108 0.005
Tags: @product
2:15.734
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.723
And I log in to a new session 12.721
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.628
And I plug USB drive "to_upgrade" 2.330
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.522
Then the running Tails is installed on USB drive "to_upgrade" 19.572
And I unplug USB drive "to_upgrade" 0.110
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.012
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.049
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.623
Then all tps features from the old Tails version are active 1.077
And Tails is running from USB drive "to_upgrade" 0.199
And the boot device has safe access rights 2.330
And the expected persistent files created with the old Tails version are present in the filesystem 1.030
And all persistent directories from the old Tails version have safe access rights 1.705
After features/support/hooks.rb:339 0.692
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:38.830
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.572
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.317
When the network is plugged 0.033
And Tor is ready 13.063
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.976
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.988
Given I shutdown Tails and wait for the computer to power off 5.396
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.910
Then Tails is running version 6.2~testoverlayfs 0.030
And all tps features are active 8.855
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.193
When the network is plugged 0.026
And Tor is ready 10.857
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.213
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.229
Given I shutdown Tails and wait for the computer to power off 4.187
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.894
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.400
And the file system changes introduced in version 6.3~testoverlayfs are present 0.495
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.036
And Tor is ready 10.475
Then the Upgrader considers the system as up-to-date 0.080
# 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.725
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.379
After features/support/hooks.rb:339 0.974
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
19.015
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.399
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.051
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.584
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.683
After features/support/hooks.rb:339 0.723
After features/support/hooks.rb:108 0.000