Project Number Date
test_Tails_ISO_20263-test-suite-disable-spice-vdagent 25 30 Mar 2025, 16:37

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 20:13.653 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:11.038
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 31.415
When I start Tails from USB drive "old" with network unplugged 1:34.019
Then the boot device has safe access rights 3.326
And Tails is running from USB drive "old" 0.338
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 6.981
After features/support/hooks.rb:100 0.036
Tags: @product
2:21.821
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 1:38.625
Then Tails is running from USB drive "old" 0.392
And I create a persistent partition 31.937
And I take note of which tps features are available 1.491
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 8.374
After features/support/hooks.rb:330 0.182
After features/support/hooks.rb:100 0.009
Tags: @product
3:3.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:27.153
Then Tails is running from USB drive "old" 0.342
And all tps features are active 1.947
When I write some files expected to persist 1.718
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.758
And I take note of which tps features are available 0.361
And I shutdown Tails and wait for the computer to power off 4.295
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.977
After features/support/hooks.rb:330 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
2:34.658
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.287
And I log in to a new session 18.883
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.004
And I plug USB drive "to_upgrade" 2.574
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.114
Then the running Tails is installed on USB drive "to_upgrade" 26.375
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:330 2.123
After features/support/hooks.rb:100 0.000
Tags: @product
2:36.600
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.165
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.280
Then all tps features from the old Tails version are active 1.543
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 3.132
And the expected persistent files created with the old Tails version are present in the filesystem 1.658
And all persistent directories from the old Tails version have safe access rights 2.532
After features/support/hooks.rb:330 1.701
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:52.455
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.644
And no SquashFS delta is installed 0.312
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.110
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.448
When the network is plugged 0.078
And Tor is ready 22.327
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.507
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.295
Given I shutdown Tails and wait for the computer to power off 8.658
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:19.221
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.244
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
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.273
# 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.292
When the network is plugged 0.065
And Tor is ready 18.049
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.609
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.673
Given I shutdown Tails and wait for the computer to power off 4.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.684
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 1.818
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.281
When the network is plugged 0.063
And Tor is ready 16.667
Then the Upgrader considers the system as up-to-date 0.335
# 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 16.095
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 3.370
After features/support/hooks.rb:330 0.668
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
33.700
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.951
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.804
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.059
And Tor is ready 16.162
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.587
After features/support/hooks.rb:330 1.067
After features/support/hooks.rb:100 0.000