Project Number Date
test_Tails_ISO_stable 4627 21 Jan 2024, 13:10

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 5:56.879 Passed
5:31.214
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.443
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.267
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.059
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.328
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.492
When the network is plugged 0.024
And Tor is ready 16.177
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.568
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.709
Given I shutdown Tails and wait for the computer to power off 5.090
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:40.899
Then Tails is running version 2.2~testoverlayfsng 0.083
And all tps features are active 1.835
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.369
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.272
# 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.263
When the network is plugged 0.029
And Tor is ready 14.729
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.557
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.721
Given I shutdown Tails and wait for the computer to power off 4.078
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.423
Then Tails is running version 2.3~testoverlayfsng 0.084
And all tps features are active 1.649
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.606
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.063
# 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.394
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.289
When the network is plugged 0.023
And Tor is ready 15.435
Then the Upgrader considers the system as up-to-date 0.276
# 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 29.457
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.338
After features/support/hooks.rb:291 0.791
After features/support/hooks.rb:75 0.021
25.665
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.004
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.315
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.553
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 15.164
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.547
After features/support/hooks.rb:291 1.066
After features/support/hooks.rb:75 0.000