Project Number Date
test_Tails_ISO_devel 3218 31 Dec 2023, 12:12

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:8.487 Passed
5:39.123
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 10.733
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.368
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.061
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.570
When the network is plugged 0.039
And Tor is ready 15.606
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.719
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.652
Given I shutdown Tails and wait for the computer to power off 6.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.640
Then Tails is running version 2.2~testoverlayfsng 0.094
And all tps features are active 2.231
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.386
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.105
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.259
# 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.302
When the network is plugged 0.036
And Tor is ready 18.070
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.629
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.708
Given I shutdown Tails and wait for the computer to power off 4.061
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.895
Then Tails is running version 2.3~testoverlayfsng 0.094
And all tps features are active 1.992
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.565
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.083
# 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.282
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.298
When the network is plugged 0.047
And Tor is ready 14.871
Then the Upgrader considers the system as up-to-date 0.263
# 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.253
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.304
After features/support/hooks.rb:291 0.730
After features/support/hooks.rb:75 0.019
29.364
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.552
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.422
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.071
And the signing key used by the Upgrader is outdated 0.496
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 16.001
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.774
After features/support/hooks.rb:291 1.035
After features/support/hooks.rb:75 0.000