Project Number Date
test_Tails_ISO_stable 4561 10 Dec 2023, 12:12

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:32.284 Passed
6:3.313
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.110
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.382
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.099
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.382
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.491
When the network is plugged 0.050
And Tor is ready 18.778
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.896
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.770
Given I shutdown Tails and wait for the computer to power off 6.327
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.687
Then Tails is running version 2.2~testoverlayfsng 0.112
And all tps features are active 2.143
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.356
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.309
When the network is plugged 0.031
And Tor is ready 15.808
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.884
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.019
Given I shutdown Tails and wait for the computer to power off 4.478
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.446
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 2.107
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.620
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.078
# 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.323
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.293
When the network is plugged 0.053
And Tor is ready 16.972
Then the Upgrader considers the system as up-to-date 0.495
# 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.617
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.538
After features/support/hooks.rb:291 0.797
After features/support/hooks.rb:75 0.019
28.971
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.240
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.364
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.056
And the signing key used by the Upgrader is outdated 1.762
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 14.829
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.673
After features/support/hooks.rb:291 0.752
After features/support/hooks.rb:75 0.000