Project Number Date
test_Tails_ISO_stable 4569 14 Dec 2023, 12:08

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 5:56.176 Passed
5:30.424
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.080
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.395
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.633
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.500
When the network is plugged 0.062
And Tor is ready 15.996
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.524
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.062
Given I shutdown Tails and wait for the computer to power off 6.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.845
Then Tails is running version 2.2~testoverlayfsng 0.098
And all tps features are active 2.379
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.350
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.267
# 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.453
When the network is plugged 0.085
And Tor is ready 15.299
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.568
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.506
Given I shutdown Tails and wait for the computer to power off 4.186
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.285
Then Tails is running version 2.3~testoverlayfsng 0.097
And all tps features are active 2.027
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.625
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.055
# 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.301
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.317
When the network is plugged 0.053
And Tor is ready 13.984
Then the Upgrader considers the system as up-to-date 0.278
# 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 24.914
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.664
After features/support/hooks.rb:291 0.737
After features/support/hooks.rb:75 0.019
25.752
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.699
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.493
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.054
And the signing key used by the Upgrader is outdated 0.335
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 13.581
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.541
After features/support/hooks.rb:291 0.736
After features/support/hooks.rb:75 0.000