Project Number Date
test_Tails_ISO_devel 3208 23 Dec 2023, 12:24

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:15.909 Passed
5:47.526
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 13.274
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.340
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.053
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.377
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.545
When the network is plugged 0.062
And Tor is ready 18.406
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.662
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.014
Given I shutdown Tails and wait for the computer to power off 6.197
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.742
Then Tails is running version 2.2~testoverlayfsng 0.111
And all tps features are active 2.275
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.448
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.408
# 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.470
When the network is plugged 0.087
And Tor is ready 17.794
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.672
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.121
Given I shutdown Tails and wait for the computer to power off 3.089
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.427
Then Tails is running version 2.3~testoverlayfsng 0.107
And all tps features are active 2.190
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.709
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.103
# 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.290
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.309
When the network is plugged 0.050
And Tor is ready 13.135
Then the Upgrader considers the system as up-to-date 10.817
# 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 25.440
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.617
After features/support/hooks.rb:291 0.987
After features/support/hooks.rb:75 0.023
28.382
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 9.629
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.337
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.059
And the signing key used by the Upgrader is outdated 0.527
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 14.954
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.840
After features/support/hooks.rb:291 0.752
After features/support/hooks.rb:75 0.000