Project Number Date
test_Tails_ISO_stable 4538 28 Nov 2023, 00:16

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:12.509 Passed
5:44.116
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.710
And no SquashFS delta is installed 0.126
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.386
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.066
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.394
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.543
When the network is plugged 0.037
And Tor is ready 16.874
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.599
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.576
Given I shutdown Tails and wait for the computer to power off 7.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.453
Then Tails is running version 2.2~testoverlayfsng 0.107
And all tps features are active 2.573
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.395
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.336
When the network is plugged 0.037
And Tor is ready 17.480
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.711
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.510
Given I shutdown Tails and wait for the computer to power off 3.091
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.880
Then Tails is running version 2.3~testoverlayfsng 0.091
And all tps features are active 2.230
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.599
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.075
# 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.260
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.355
When the network is plugged 0.035
And Tor is ready 15.085
Then the Upgrader considers the system as up-to-date 0.285
# 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.350
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.165
After features/support/hooks.rb:291 0.752
After features/support/hooks.rb:75 0.023
28.392
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.130
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.343
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the signing key used by the Upgrader is outdated 0.447
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 14.549
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.806
After features/support/hooks.rb:291 1.505
After features/support/hooks.rb:75 0.000