Project Number Date
test_Tails_ISO_post-7.14-release-process 3 30 Sep 2026, 02:17

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:5.524 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:4.087
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 13.162
When I start Tails from USB drive "old" with network unplugged 46.952
Then the boot device has safe access rights 2.209
And Tails is running from USB drive "old" 0.190
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.026
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 1.329
After features/support/hooks.rb:108 0.006
Tags: @product
1:23.720
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login 48.932
Then Tails is running from USB drive "old" 0.174
And I create a persistent partition 23.504
And I take note of which tps features are available 6.520
Then a Tails persistence partition exists on USB drive "old" 0.562
And I shutdown Tails and wait for the computer to power off 3.916
After features/support/hooks.rb:339 0.131
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.662
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.433
Then Tails is running from USB drive "old" 0.221
And all tps features are active 6.813
When I write some files expected to persist 1.066
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 1.830
And I take note of which tps features are available 6.275
And I shutdown Tails and wait for the computer to power off 5.086
# 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.322
After features/support/hooks.rb:339 0.143
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.036
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.577
And I log in to a new session 11.475
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.721
And I plug USB drive "to_upgrade" 2.181
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.927
Then the running Tails is installed on USB drive "to_upgrade" 16.918
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.840
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.760
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.275
Then all tps features from the old Tails version are active 1.096
And Tails is running from USB drive "to_upgrade" 0.163
And the boot device has safe access rights 2.489
And the expected persistent files created with the old Tails version are present in the filesystem 1.065
And all persistent directories from the old Tails version have safe access rights 1.588
After features/support/hooks.rb:339 0.941
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
3:26.027
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.260
And no SquashFS delta is installed 0.064
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.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.034
And Tor is ready 12.866
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.954
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.403
Given I shutdown Tails and wait for the computer to power off 5.248
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.298
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.031
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.173
When the network is plugged 0.033
And Tor is ready 10.506
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.393
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.845
Given I shutdown Tails and wait for the computer to power off 2.640
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.907
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.615
And the file system changes introduced in version 6.3~testoverlayfs are present 0.368
And only the 6.3~testoverlayfs SquashFS delta is installed 0.027
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.142
When the network is plugged 0.029
And Tor is ready 10.386
Then the Upgrader considers the system as up-to-date 0.069
# 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.073
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.326
After features/support/hooks.rb:339 0.789
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.229
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.960
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.599
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.323
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.000