Project Number Date
test_Tails_ISO_stable 4522 23 Nov 2023, 12:28

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:10.207 Passed
6:36.166
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.296
And no SquashFS delta is installed 0.205
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.433
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.403
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.555
When the network is plugged 0.038
And Tor is ready 17.505
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.842
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.010
Given I shutdown Tails and wait for the computer to power off 8.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.843
Then Tails is running version 2.2~testoverlayfsng 0.121
And all tps features are active 10.367
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.466
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.107
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.311
When the network is plugged 0.041
And Tor is ready 17.008
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.722
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.639
Given I shutdown Tails and wait for the computer to power off 4.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.647
Then Tails is running version 2.3~testoverlayfsng 0.141
And all tps features are active 19.539
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.572
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.083
# 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.542
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.300
When the network is plugged 0.062
And Tor is ready 16.463
Then the Upgrader considers the system as up-to-date 0.271
# 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.030
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.449
After features/support/hooks.rb:290 1.057
After features/support/hooks.rb:75 0.019
34.041
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 14.420
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.635
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.131
And the signing key used by the Upgrader is outdated 0.634
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 17.513
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.641
After features/support/hooks.rb:290 0.787
After features/support/hooks.rb:75 0.000