Project Number Date
test_Tails_ISO_stable 4525 23 Nov 2023, 17:31

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:47.515 Passed
6:18.023
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.295
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.305
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.061
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.463
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.916
When the network is plugged 0.097
And Tor is ready 16.168
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.000
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.542
Given I shutdown Tails and wait for the computer to power off 6.293
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:58.116
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 10.420
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.497
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.089
# 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.343
When the network is plugged 0.041
And Tor is ready 16.037
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.715
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.172
Given I shutdown Tails and wait for the computer to power off 4.068
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.915
Then Tails is running version 2.3~testoverlayfsng 0.093
And all tps features are active 8.558
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.639
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.087
# 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.307
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.334
When the network is plugged 0.043
And Tor is ready 18.346
Then the Upgrader considers the system as up-to-date 0.298
# 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.704
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.497
After features/support/hooks.rb:290 0.843
After features/support/hooks.rb:75 0.020
29.492
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 10.348
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.401
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.071
And the signing key used by the Upgrader is outdated 1.249
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 14.670
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.716
After features/support/hooks.rb:290 0.694
After features/support/hooks.rb:75 0.000