Project Number Date
test_Tails_ISO_devel 4065 11 Nov 2025, 10:44

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 17:26.330 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:59.767
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.209
And I create a 7200 MiB disk named "old" 0.074
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 35.031
When I start Tails from USB drive "old" with network unplugged 1:19.558
Then the boot device has safe access rights 2.957
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.252
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:331 3.619
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.400
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 1:28.574
Then Tails is running from USB drive "old" 0.743
And I create a persistent partition 30.806
And I take note of which tps features are available 1.443
Then a Tails persistence partition exists on USB drive "old" 0.687
And I shutdown Tails and wait for the computer to power off 7.951
After features/support/hooks.rb:331 0.652
After features/support/hooks.rb:100 0.009
Tags: @product
2:14.515
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.300
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.773
Then Tails is running from USB drive "old" 0.696
And all tps features are active 2.119
When I write some files expected to persist 1.697
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.388
And all persistent directories from the old Tails version have safe access rights 2.190
And I take note of which tps features are available 0.496
And I shutdown Tails and wait for the computer to power off 7.768
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.870
After features/support/hooks.rb:331 0.584
After features/support/hooks.rb:100 0.013
Tags: @product
2:45.401
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 14.924
And I log in to a new session 18.643
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.156
And I plug USB drive "to_upgrade" 2.501
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.455
Then the running Tails is installed on USB drive "to_upgrade" 23.231
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.273
After features/support/hooks.rb:331 3.782
After features/support/hooks.rb:100 0.000
Tags: @product
1:53.924
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.473
Then all tps features from the old Tails version are active 1.892
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.352
And the expected persistent files created with the old Tails version are present in the filesystem 1.610
And all persistent directories from the old Tails version have safe access rights 3.017
After features/support/hooks.rb:331 1.162
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:27.736
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 14.005
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.061
And Tor is ready 15.519
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.622
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.141
Given I shutdown Tails and wait for the computer to power off 9.995
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.575
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.830
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
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.212
# 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.384
When the network is plugged 0.077
And Tor is ready 12.839
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.589
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.606
Given I shutdown Tails and wait for the computer to power off 8.120
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.234
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.790
And the file system changes introduced in version 6.3~testoverlayfs are present 0.624
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.178
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.083
And Tor is ready 13.718
Then the Upgrader considers the system as up-to-date 0.462
# 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 10.280
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.910
After features/support/hooks.rb:331 1.077
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
54.585
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 12.347
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.432
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 41.033
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.578
After features/support/hooks.rb:331 0.865
After features/support/hooks.rb:100 0.000