Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 88 28 May 2024, 06:59

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:47.800 Passed
7:11.667
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 31.325
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.459
And Tor is ready 17.958
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.304
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.415
Given I shutdown Tails and wait for the computer to power off 11.420
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.541
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 6.956
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.304
When the network is plugged 0.471
And Tor is ready 19.361
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.982
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.834
Given I shutdown Tails and wait for the computer to power off 6.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.466
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.145
And the file system changes introduced in version 6.3~testoverlayfs are present 0.615
And only the 6.3~testoverlayfs SquashFS delta is installed 0.091
# 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.615
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.042
And Tor is ready 19.008
Then the Upgrader considers the system as up-to-date 0.347
# 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.416
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.905
After features/support/hooks.rb:305 0.787
After features/support/hooks.rb:89 0.024
36.132
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.420
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.314
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.602
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 18.950
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.731
After features/support/hooks.rb:305 0.784
After features/support/hooks.rb:89 0.000