Project Number Date
test_Tails_ISO_stable 4626 20 Jan 2024, 12:49

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:41.138 Passed
6:12.863
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.982
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.295
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.057
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.496
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.530
When the network is plugged 0.019
And Tor is ready 17.409
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.683
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.923
Given I shutdown Tails and wait for the computer to power off 5.248
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.737
Then Tails is running version 2.2~testoverlayfsng 0.115
And all tps features are active 1.781
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.438
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.258
When the network is plugged 0.032
And Tor is ready 42.108
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.520
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.486
Given I shutdown Tails and wait for the computer to power off 4.308
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.612
Then Tails is running version 2.3~testoverlayfsng 0.110
And all tps features are active 1.669
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.536
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.061
# 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.280
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.270
When the network is plugged 0.021
And Tor is ready 16.458
Then the Upgrader considers the system as up-to-date 0.243
# 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.429
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.269
After features/support/hooks.rb:291 0.716
After features/support/hooks.rb:75 0.018
28.275
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.451
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.323
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.047
And the signing key used by the Upgrader is outdated 1.250
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 14.564
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.607
After features/support/hooks.rb:291 0.670
After features/support/hooks.rb:75 0.000