Project Number Date
test_Tails_ISO_stable 4677 21 Feb 2024, 12:23

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:28.913 Passed
5:59.645
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 11.162
And no SquashFS delta is installed 0.142
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.332
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.070
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.414
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.590
When the network is plugged 0.036
And Tor is ready 17.277
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.676
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.043
Given I shutdown Tails and wait for the computer to power off 9.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.270
Then Tails is running version 2.2~testoverlayfsng 0.116
And all tps features are active 2.661
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.433
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.354
When the network is plugged 0.042
And Tor is ready 16.720
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.658
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.333
Given I shutdown Tails and wait for the computer to power off 4.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.193
Then Tails is running version 2.3~testoverlayfsng 0.115
And all tps features are active 2.269
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.667
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.336
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.402
When the network is plugged 0.046
And Tor is ready 15.622
Then the Upgrader considers the system as up-to-date 0.289
# 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.542
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.990
After features/support/hooks.rb:291 0.783
After features/support/hooks.rb:75 0.023
29.268
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.378
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.340
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.078
And the signing key used by the Upgrader is outdated 0.549
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 17.195
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.662
After features/support/hooks.rb:291 1.053
After features/support/hooks.rb:75 0.000