Project Number Date
test_Tails_ISO_devel 3868 14 Jun 2025, 13:45

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 22:29.239 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
2:39.057
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 36.646
When I start Tails from USB drive "old" with network unplugged 1:56.185
Then the boot device has safe access rights 3.817
And Tails is running from USB drive "old" 0.415
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.321
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:330 7.343
After features/support/hooks.rb:100 0.010
Tags: @product
2:27.412
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:39.120
Then Tails is running from USB drive "old" 0.380
And I create a persistent partition 36.237
And I take note of which tps features are available 1.947
Then a Tails persistence partition exists on USB drive "old" 1.001
And I shutdown Tails and wait for the computer to power off 8.533
After features/support/hooks.rb:330 0.281
After features/support/hooks.rb:100 0.014
Tags: @product
3:26.008
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.028
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:40.807
Then Tails is running from USB drive "old" 0.391
And all tps features are active 2.419
When I write some files expected to persist 2.671
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.262
And all persistence configuration files have safe access rights 0.433
And all persistent directories from the old Tails version have safe access rights 2.826
And I take note of which tps features are available 0.535
And I shutdown Tails and wait for the computer to power off 6.355
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 29.097
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.039
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 12.100
And I log in to a new session 21.844
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.277
And I plug USB drive "to_upgrade" 2.516
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.442
Then the running Tails is installed on USB drive "to_upgrade" 34.348
And I unplug USB drive "to_upgrade" 0.294
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:330 3.306
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.221
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:24.431
Then all tps features from the old Tails version are active 1.721
And Tails is running from USB drive "to_upgrade" 0.463
And the boot device has safe access rights 5.943
And the expected persistent files created with the old Tails version are present in the filesystem 1.835
And all persistent directories from the old Tails version have safe access rights 2.821
After features/support/hooks.rb:330 1.641
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:40.070
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.861
And no SquashFS delta is installed 0.317
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.668
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.136
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.410
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.764
When the network is plugged 0.146
And Tor is ready 28.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.817
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.828
Given I shutdown Tails and wait for the computer to power off 12.542
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.615
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.188
And the file system changes introduced in version 6.2~testoverlayfs are present 0.390
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.493
When the network is plugged 0.095
And Tor is ready 22.107
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.527
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.058
Given I shutdown Tails and wait for the computer to power off 6.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:24.437
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.449
And the file system changes introduced in version 6.3~testoverlayfs are present 0.680
And only the 6.3~testoverlayfs SquashFS delta is installed 0.116
# 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.417
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.071
And Tor is ready 20.433
Then the Upgrader considers the system as up-to-date 0.294
# 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 18.197
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.890
After features/support/hooks.rb:330 0.765
After features/support/hooks.rb:100 0.056
Tags: @product @automatic_upgrade
42.211
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 11.449
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.465
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.095
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 22.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.336
After features/support/hooks.rb:330 1.084
After features/support/hooks.rb:100 0.000