Project Number Date
test_Tails_ISO_stable 4672 18 Feb 2024, 12: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 7:26.615 Passed
6:33.287
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 11.134
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.314
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.320
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.596
When the network is plugged 0.048
And Tor is ready 15.745
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.656
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.986
Given I shutdown Tails and wait for the computer to power off 6.353
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.488
Then Tails is running version 2.2~testoverlayfsng 0.122
And all tps features are active 2.413
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.494
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.106
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.334
# 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.290
When the network is plugged 0.033
And Tor is ready 14.453
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.699
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.900
Given I shutdown Tails and wait for the computer to power off 4.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.635
Then Tails is running version 2.3~testoverlayfsng 0.095
And all tps features are active 2.254
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.573
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.073
# 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.318
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.340
When the network is plugged 0.038
And Tor is ready 42.537
Then the Upgrader considers the system as up-to-date 0.252
# 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.145
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.058
After features/support/hooks.rb:291 0.845
After features/support/hooks.rb:75 0.021
53.328
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 9.971
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.086
And the signing key used by the Upgrader is outdated 0.631
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 41.647
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.637
After features/support/hooks.rb:291 1.341
After features/support/hooks.rb:75 0.000