Project Number Date
test_Tails_ISO_devel 3188 10 Dec 2023, 12:26

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:1.352 Passed
5:35.367
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.715
And no SquashFS delta is installed 0.296
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.261
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.055
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.347
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.545
When the network is plugged 0.042
And Tor is ready 15.142
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.703
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.280
Given I shutdown Tails and wait for the computer to power off 5.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.041
Then Tails is running version 2.2~testoverlayfsng 0.121
And all tps features are active 2.220
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.418
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.293
# 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.274
When the network is plugged 0.036
And Tor is ready 15.600
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.554
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.233
Given I shutdown Tails and wait for the computer to power off 4.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.349
Then Tails is running version 2.3~testoverlayfsng 0.122
And all tps features are active 2.109
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.602
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.278
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.296
When the network is plugged 0.057
And Tor is ready 13.806
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 26.964
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.592
After features/support/hooks.rb:291 0.740
After features/support/hooks.rb:75 0.018
25.985
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 9.577
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.456
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.060
And the signing key used by the Upgrader is outdated 0.440
But a current signing key is available on our website 0.000
When the network is plugged 0.058
And Tor is ready 13.650
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.741
After features/support/hooks.rb:291 0.769
After features/support/hooks.rb:75 0.000