Project Number Date
test_Tails_ISO_stable 4571 17 Dec 2023, 12:01

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:49.295 Passed
5:21.903
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.505
And no SquashFS delta is installed 0.142
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.316
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.089
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.404
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.525
When the network is plugged 0.053
And Tor is ready 14.528
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.561
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.797
Given I shutdown Tails and wait for the computer to power off 5.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.452
Then Tails is running version 2.2~testoverlayfsng 0.112
And all tps features are active 2.321
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.383
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.294
# 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.262
When the network is plugged 0.041
And Tor is ready 14.201
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.608
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.298
Given I shutdown Tails and wait for the computer to power off 3.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.779
Then Tails is running version 2.3~testoverlayfsng 0.090
And all tps features are active 2.028
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.598
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.061
# 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.291
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.308
When the network is plugged 0.055
And Tor is ready 13.743
Then the Upgrader considers the system as up-to-date 0.255
# 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.085
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.220
After features/support/hooks.rb:291 1.085
After features/support/hooks.rb:75 0.019
27.391
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.334
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.403
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.599
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 14.344
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.601
After features/support/hooks.rb:291 0.652
After features/support/hooks.rb:75 0.000