Project Number Date
test_Tails_ISO_stable 4657 08 Feb 2024, 19:02

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:43.783 Passed
6:14.663
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 11.427
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.399
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.084
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.528
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.732
When the network is plugged 0.045
And Tor is ready 17.592
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.944
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.800
Given I shutdown Tails and wait for the computer to power off 6.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.043
Then Tails is running version 2.2~testoverlayfsng 0.106
And all tps features are active 2.237
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.419
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.089
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.297
# 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.322
When the network is plugged 0.043
And Tor is ready 16.025
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.987
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.941
Given I shutdown Tails and wait for the computer to power off 4.498
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.612
Then Tails is running version 2.3~testoverlayfsng 0.100
And all tps features are active 2.232
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.722
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.089
# 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.312
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.352
When the network is plugged 0.031
And Tor is ready 16.901
Then the Upgrader considers the system as up-to-date 10.821
# 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.021
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.485
After features/support/hooks.rb:291 0.856
After features/support/hooks.rb:75 0.018
29.119
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.736
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.379
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.063
And the signing key used by the Upgrader is outdated 0.578
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 15.605
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.719
After features/support/hooks.rb:291 0.964
After features/support/hooks.rb:75 0.000