Project Number Date
test_Tails_ISO_stable 4579 20 Dec 2023, 13:33

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 7:0.069 Passed
6:4.384
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 17.106
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.516
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.083
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.426
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.542
When the network is plugged 0.042
And Tor is ready 18.128
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.691
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.535
Given I shutdown Tails and wait for the computer to power off 6.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.536
Then Tails is running version 2.2~testoverlayfsng 0.125
And all tps features are active 2.316
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.475
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.390
# 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.372
When the network is plugged 0.052
And Tor is ready 16.119
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.723
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.031
Given I shutdown Tails and wait for the computer to power off 4.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.426
Then Tails is running version 2.3~testoverlayfsng 0.160
And all tps features are active 2.366
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.703
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.090
# 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.379
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.367
When the network is plugged 0.080
And Tor is ready 16.832
Then the Upgrader considers the system as up-to-date 0.313
# 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 26.129
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.358
After features/support/hooks.rb:291 0.812
After features/support/hooks.rb:75 0.027
55.685
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 10.619
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.442
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.067
And the signing key used by the Upgrader is outdated 0.496
But a current signing key is available on our website 0.000
When the network is plugged 0.091
And Tor is ready 43.308
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.659
After features/support/hooks.rb:291 1.324
After features/support/hooks.rb:75 0.000