Project Number Date
test_Tails_ISO_stable 4549 04 Dec 2023, 19:42

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:43.002 Passed
5:47.233
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.623
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.312
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.090
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.389
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.594
When the network is plugged 0.049
And Tor is ready 15.463
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.589
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.849
Given I shutdown Tails and wait for the computer to power off 6.292
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.103
Then Tails is running version 2.2~testoverlayfsng 0.104
And all tps features are active 2.261
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.363
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.283
When the network is plugged 0.048
And Tor is ready 14.987
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.530
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.217
Given I shutdown Tails and wait for the computer to power off 4.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.504
Then Tails is running version 2.3~testoverlayfsng 0.120
And all tps features are active 2.376
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.584
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.287
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.280
When the network is plugged 0.051
And Tor is ready 17.468
Then the Upgrader considers the system as up-to-date 0.580
# 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 24.865
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.061
After features/support/hooks.rb:291 0.747
After features/support/hooks.rb:75 0.018
55.769
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 9.417
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.300
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.055
And the signing key used by the Upgrader is outdated 1.498
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 43.887
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.561
After features/support/hooks.rb:291 0.650
After features/support/hooks.rb:75 0.000