Project Number Date
test_Tails_ISO_stable 4659 09 Feb 2024, 18:31

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.295 Passed
5:57.558
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.307
And no SquashFS delta is installed 0.116
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.397
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.069
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.411
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.563
When the network is plugged 0.058
And Tor is ready 20.668
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.715
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.192
Given I shutdown Tails and wait for the computer to power off 5.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.045
Then Tails is running version 2.2~testoverlayfsng 0.127
And all tps features are active 2.288
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.463
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.289
# 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.352
When the network is plugged 0.044
And Tor is ready 15.504
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.692
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.082
Given I shutdown Tails and wait for the computer to power off 3.617
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.741
Then Tails is running version 2.3~testoverlayfsng 0.179
And all tps features are active 2.151
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.672
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.066
# 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.326
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 14.444
Then the Upgrader considers the system as up-to-date 10.733
# 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.497
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.910
After features/support/hooks.rb:291 0.748
After features/support/hooks.rb:75 0.052
30.737
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.069
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.413
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.058
And the signing key used by the Upgrader is outdated 0.964
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 16.389
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.806
After features/support/hooks.rb:291 1.275
After features/support/hooks.rb:75 0.000