Project Number Date
test_Tails_ISO_stable 4552 05 Dec 2023, 15:24

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:23.221 Passed
5:56.681
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 12.127
And no SquashFS delta is installed 0.265
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.365
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.371
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.617
When the network is plugged 0.028
And Tor is ready 17.419
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.748
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.697
Given I shutdown Tails and wait for the computer to power off 7.295
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.144
Then Tails is running version 2.2~testoverlayfsng 0.101
And all tps features are active 1.924
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.437
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.300
When the network is plugged 0.022
And Tor is ready 19.145
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.676
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.063
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.125
Then Tails is running version 2.3~testoverlayfsng 0.145
And all tps features are active 1.897
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.653
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.110
# 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.314
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.338
When the network is plugged 0.032
And Tor is ready 18.967
Then the Upgrader considers the system as up-to-date 0.307
# 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 26.023
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.235
After features/support/hooks.rb:291 0.765
After features/support/hooks.rb:75 0.019
26.539
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.861
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.372
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.089
And the signing key used by the Upgrader is outdated 0.738
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 12.533
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.919
After features/support/hooks.rb:291 0.737
After features/support/hooks.rb:75 0.000