Project Number Date
test_Tails_ISO_stable 4575 18 Dec 2023, 18:05

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 6:56.953 Passed
6:26.276
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.478
And no SquashFS delta is installed 0.297
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.323
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.071
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.416
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.585
When the network is plugged 0.050
And Tor is ready 18.840
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 4.094
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.849
Given I shutdown Tails and wait for the computer to power off 6.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.300
Then Tails is running version 2.2~testoverlayfsng 0.137
And all tps features are active 2.579
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.485
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# We'll really install Tails_amd64_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.291
When the network is plugged 0.046
And Tor is ready 44.638
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.555
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.145
Given I shutdown Tails and wait for the computer to power off 4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.847
Then Tails is running version 2.3~testoverlayfsng 0.103
And all tps features are active 2.612
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.652
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.076
# 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.322
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.304
When the network is plugged 0.043
And Tor is ready 15.175
Then the Upgrader considers the system as up-to-date 0.268
# 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 30.461
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.221
After features/support/hooks.rb:291 0.835
After features/support/hooks.rb:75 0.041
30.676
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.039
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.569
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.076
And the signing key used by the Upgrader is outdated 1.985
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 16.360
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.601
After features/support/hooks.rb:291 0.800
After features/support/hooks.rb:75 0.000