Project Number Date
test_Tails_ISO_post-7.14-release-process 2 29 Sep 2026, 21:54

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:41.705 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:7.464
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.730
When I start Tails from USB drive "old" with network unplugged 49.546
Then the boot device has safe access rights 2.421
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 1.257
After features/support/hooks.rb:108 0.008
Tags: @product
1:26.184
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login 51.613
Then Tails is running from USB drive "old" 0.221
And I create a persistent partition 24.235
And I take note of which tps features are available 6.664
Then a Tails persistence partition exists on USB drive "old" 0.552
And I shutdown Tails and wait for the computer to power off 2.803
After features/support/hooks.rb:339 0.215
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.039
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.122
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.952
Then Tails is running from USB drive "old" 0.414
And all tps features are active 7.696
When I write some files expected to persist 1.225
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.356
And all persistent directories from the old Tails version have safe access rights 1.765
And I take note of which tps features are available 7.039
And I shutdown Tails and wait for the computer to power off 4.202
# 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" 13.091
After features/support/hooks.rb:339 0.303
After features/support/hooks.rb:108 0.013
Tags: @product
2:14.768
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.659
And I log in to a new session 12.396
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.716
And I plug USB drive "to_upgrade" 2.277
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.746
Then the running Tails is installed on USB drive "to_upgrade" 18.731
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.452
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.615
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.141
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.298
Then all tps features from the old Tails version are active 1.176
And Tails is running from USB drive "to_upgrade" 0.212
And the boot device has safe access rights 2.529
And the expected persistent files created with the old Tails version are present in the filesystem 1.244
And all persistent directories from the old Tails version have safe access rights 2.010
After features/support/hooks.rb:339 0.684
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
3:40.989
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.481
And no SquashFS delta is installed 0.049
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.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.547
When the network is plugged 0.026
And Tor is ready 13.264
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.907
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.560
Given I shutdown Tails and wait for the computer to power off 7.211
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.333
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.953
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
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.144
# 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.212
When the network is plugged 0.025
And Tor is ready 10.565
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.323
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.743
Given I shutdown Tails and wait for the computer to power off 4.131
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.294
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.641
And the file system changes introduced in version 6.3~testoverlayfs are present 0.337
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.031
And Tor is ready 10.618
Then the Upgrader considers the system as up-to-date 0.112
# 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.746
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:339 1.349
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.644
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.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.983
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.030
After features/support/hooks.rb:339 0.503
After features/support/hooks.rb:108 0.000