Project Number Date
test_Tails_ISO_stable 4655 07 Feb 2024, 22:01

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:2.458 Passed
5:35.039
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.208
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.324
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.086
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.408
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.715
When the network is plugged 0.027
And Tor is ready 15.659
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.754
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.904
Given I shutdown Tails and wait for the computer to power off 5.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.599
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 1.733
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.466
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.382
When the network is plugged 0.022
And Tor is ready 15.303
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.631
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.828
Given I shutdown Tails and wait for the computer to power off 4.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.015
Then Tails is running version 2.3~testoverlayfsng 0.094
And all tps features are active 1.715
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.560
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.069
# 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.308
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 18.280
Then the Upgrader considers the system as up-to-date 0.349
# 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 24.999
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.352
After features/support/hooks.rb:291 0.761
After features/support/hooks.rb:75 0.018
27.418
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.324
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.058
And the signing key used by the Upgrader is outdated 0.460
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 14.407
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.758
After features/support/hooks.rb:291 0.917
After features/support/hooks.rb:75 0.000