Project Number Date
test_Tails_ISO_stable 4671 17 Feb 2024, 11:59

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:44.683 Passed
6:16.327
Before features/support/hooks.rb:245 0.023
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.335
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.416
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.428
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.660
When the network is plugged 0.035
And Tor is ready 19.671
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.941
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.978
Given I shutdown Tails and wait for the computer to power off 11.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.588
Then Tails is running version 2.2~testoverlayfsng 0.115
And all tps features are active 2.272
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.434
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.320
When the network is plugged 0.034
And Tor is ready 14.488
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.913
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.688
Given I shutdown Tails and wait for the computer to power off 3.382
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.243
Then Tails is running version 2.3~testoverlayfsng 0.141
And all tps features are active 2.527
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.570
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.373
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.344
When the network is plugged 0.052
And Tor is ready 13.647
Then the Upgrader considers the system as up-to-date 10.893
# 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 27.832
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.083
After features/support/hooks.rb:291 0.848
After features/support/hooks.rb:75 0.021
28.356
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.081
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.410
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.107
And the signing key used by the Upgrader is outdated 0.684
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 15.302
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.734
After features/support/hooks.rb:291 1.345
After features/support/hooks.rb:75 0.000