Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 106 14 Jun 2024, 15:16

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@automatic_upgrade 43 0 0 0 0 43 2 0 2 7:48.781 Passed
6:57.099
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.477
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.556
When the network is plugged 0.079
And Tor is ready 21.087
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.891
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.266
Given I shutdown Tails and wait for the computer to power off 9.043
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.752
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.419
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.375
# 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.303
When the network is plugged 0.034
And Tor is ready 20.103
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.632
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.531
Given I shutdown Tails and wait for the computer to power off 4.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.707
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.203
And the file system changes introduced in version 6.3~testoverlayfs are present 0.544
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.033
And Tor is ready 16.340
Then the Upgrader considers the system as up-to-date 0.310
# 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 14.109
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.006
After features/support/hooks.rb:320 0.697
After features/support/hooks.rb:100 0.023
51.682
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.520
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 1.709
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 18.911
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.019
After features/support/hooks.rb:320 0.708
After features/support/hooks.rb:100 0.000