Project Number Date
test_Tails_ISO_stable 4597 31 Dec 2023, 12:06

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:20.743 Passed
5:55.447
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 11.415
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.360
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.087
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.362
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.628
When the network is plugged 0.045
And Tor is ready 21.036
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.615
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.934
Given I shutdown Tails and wait for the computer to power off 6.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.761
Then Tails is running version 2.2~testoverlayfsng 0.115
And all tps features are active 2.416
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.353
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.290
When the network is plugged 0.033
And Tor is ready 17.027
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.664
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.205
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.891
Then Tails is running version 2.3~testoverlayfsng 0.127
And all tps features are active 1.939
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.569
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.067
# 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.269
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.426
When the network is plugged 0.048
And Tor is ready 17.043
Then the Upgrader considers the system as up-to-date 0.248
# 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.326
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.122
After features/support/hooks.rb:291 0.736
After features/support/hooks.rb:75 0.035
25.296
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 9.346
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.066
And the signing key used by the Upgrader is outdated 1.255
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 11.578
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.657
After features/support/hooks.rb:291 0.684
After features/support/hooks.rb:75 0.000