Project Number Date
test_Tails_ISO_post-7.15.1-release-process 1 23 Oct 2026, 16:14

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:18.517 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:3.373
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given a computer 0.172
And I create a 7200 MiB disk named "old" 0.029
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.491
When I start Tails from USB drive "old" with network unplugged 45.863
Then the boot device has safe access rights 2.169
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.173
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.707
After features/support/hooks.rb:108 0.014
Tags: @product
1:24.259
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login 49.249
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 24.314
And I take note of which tps features are available 7.156
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 2.654
After features/support/hooks.rb:339 0.589
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.602
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 58.977
Then Tails is running from USB drive "old" 0.222
And all tps features are active 6.775
When I write some files expected to persist 1.113
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.939
And I take note of which tps features are available 6.311
And I shutdown Tails and wait for the computer to power off 2.606
# 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.162
After features/support/hooks.rb:339 0.203
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.329
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.737
And I log in to a new session 11.763
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.713
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.187
Then the running Tails is installed on USB drive "to_upgrade" 18.422
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.810
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.877
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.429
Then all tps features from the old Tails version are active 1.012
And Tails is running from USB drive "to_upgrade" 0.163
And the boot device has safe access rights 2.567
And the expected persistent files created with the old Tails version are present in the filesystem 0.888
And all persistent directories from the old Tails version have safe access rights 1.719
After features/support/hooks.rb:339 0.841
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:41.366
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 21.438
And no SquashFS delta is installed 0.064
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.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.214
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.346
When the network is plugged 0.029
And Tor is ready 12.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.870
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.554
Given I shutdown Tails and wait for the computer to power off 5.250
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.545
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 7.551
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.108
# 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.214
When the network is plugged 0.025
And Tor is ready 10.299
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.462
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.710
Given I shutdown Tails and wait for the computer to power off 2.770
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.451
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.633
And the file system changes introduced in version 6.3~testoverlayfs are present 0.316
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.152
When the network is plugged 0.026
And Tor is ready 10.225
Then the Upgrader considers the system as up-to-date 0.110
# 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.596
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.339
After features/support/hooks.rb:339 0.958
After features/support/hooks.rb:108 0.048
Tags: @product @automatic_upgrade
18.708
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.876
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.031
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.523
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.989
After features/support/hooks.rb:339 0.987
After features/support/hooks.rb:108 0.000