Project Number Date
test_Tails_ISO_devel 4151 05 Jan 2026, 19: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 13:58.068 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:21.445
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.244
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 27.644
When I start Tails from USB drive "old" with network unplugged 48.297
Then the boot device has safe access rights 3.270
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:331 3.970
After features/support/hooks.rb:100 0.012
Tags: @product
1:41.246
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:2.098
Then Tails is running from USB drive "old" 0.322
And I create a persistent partition 28.865
And I take note of which tps features are available 1.174
Then a Tails persistence partition exists on USB drive "old" 0.709
And I shutdown Tails and wait for the computer to power off 7.901
After features/support/hooks.rb:331 0.275
After features/support/hooks.rb:100 0.009
Tags: @product
1:59.465
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:19.981
Then Tails is running from USB drive "old" 0.347
And all tps features are active 1.982
When I write some files expected to persist 1.576
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.411
And all persistent directories from the old Tails version have safe access rights 7.185
And I take note of which tps features are available 0.591
And I shutdown Tails and wait for the computer to power off 8.605
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.404
After features/support/hooks.rb:331 0.328
After features/support/hooks.rb:100 0.010
Tags: @product
2:26.044
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.384
And I log in to a new session 11.082
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.417
And I plug USB drive "to_upgrade" 2.688
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.185
Then the running Tails is installed on USB drive "to_upgrade" 18.909
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:331 3.728
After features/support/hooks.rb:100 0.000
Tags: @product
1:29.801
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.183
Then all tps features from the old Tails version are active 1.640
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 3.644
And the expected persistent files created with the old Tails version are present in the filesystem 1.467
And all persistent directories from the old Tails version have safe access rights 2.395
After features/support/hooks.rb:331 1.184
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:39.525
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.496
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 0.059
And Tor is ready 13.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.709
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.226
Given I shutdown Tails and wait for the computer to power off 8.015
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.579
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.649
And the file system changes introduced in version 6.2~testoverlayfs are present 0.375
And only the 6.2~testoverlayfs SquashFS delta is installed 0.097
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.222
# 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.268
When the network is plugged 0.081
And Tor is ready 14.167
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.883
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.323
Given I shutdown Tails and wait for the computer to power off 3.206
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.838
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.745
And the file system changes introduced in version 6.3~testoverlayfs are present 0.557
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.185
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.094
And Tor is ready 42.322
Then the Upgrader considers the system as up-to-date 0.177
# 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 5.910
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.497
After features/support/hooks.rb:331 0.931
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
20.540
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.975
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.070
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 10.528
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.581
After features/support/hooks.rb:331 2.257
After features/support/hooks.rb:100 0.000