Project Number Date
test_Tails_ISO_devel 3177 24 Nov 2023, 03:13

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:31.341 Passed
6:4.497
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 12.467
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.436
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.092
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.441
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.591
When the network is plugged 0.031
And Tor is ready 16.726
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.752
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.978
Given I shutdown Tails and wait for the computer to power off 6.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.837
Then Tails is running version 2.2~testoverlayfsng 0.160
And all tps features are active 6.825
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.407
And only the 2.2~testoverlayfsng 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.471
# 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.373
When the network is plugged 0.023
And Tor is ready 18.762
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.595
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.266
Given I shutdown Tails and wait for the computer to power off 4.096
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.712
Then Tails is running version 2.3~testoverlayfsng 0.129
And all tps features are active 6.176
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.601
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.106
# 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 2.1~testoverlayfsng was initially installed 0.308
When the network is plugged 0.019
And Tor is ready 15.076
Then the Upgrader considers the system as up-to-date 0.390
# 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 28.564
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.204
After features/support/hooks.rb:290 0.741
After features/support/hooks.rb:75 0.023
26.843
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.826
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.490
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.062
And the signing key used by the Upgrader is outdated 0.599
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 14.164
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.672
After features/support/hooks.rb:290 0.649
After features/support/hooks.rb:75 0.000