Project Number Date
test_Tails_ISO_stable 4545 01 Dec 2023, 12:32

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:34.372 Passed
6:5.625
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.070
And no SquashFS delta is installed 0.415
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.351
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.401
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.554
When the network is plugged 0.072
And Tor is ready 15.794
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.670
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.558
Given I shutdown Tails and wait for the computer to power off 13.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.777
Then Tails is running version 2.2~testoverlayfsng 0.120
And all tps features are active 2.247
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.381
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.290
# 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.323
When the network is plugged 0.040
And Tor is ready 16.777
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.677
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.505
Given I shutdown Tails and wait for the computer to power off 3.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.440
Then Tails is running version 2.3~testoverlayfsng 0.109
And all tps features are active 2.198
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.625
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.060
# 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.301
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.404
When the network is plugged 0.052
And Tor is ready 14.288
Then the Upgrader considers the system as up-to-date 10.729
# 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 28.656
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.048
After features/support/hooks.rb:291 0.762
After features/support/hooks.rb:75 0.021
28.747
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 10.506
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.366
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.074
And the signing key used by the Upgrader is outdated 0.532
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 15.516
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.703
After features/support/hooks.rb:291 1.500
After features/support/hooks.rb:75 0.000