Project Number Date
test_Tails_ISO_devel 3200 18 Dec 2023, 18:30

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:39.162 Passed
6:9.254
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 11.710
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.478
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.083
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.387
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.559
When the network is plugged 0.046
And Tor is ready 16.520
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.671
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.993
Given I shutdown Tails and wait for the computer to power off 6.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.198
Then Tails is running version 2.2~testoverlayfsng 0.105
And all tps features are active 2.350
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.459
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.291
When the network is plugged 0.039
And Tor is ready 15.414
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.713
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.927
Given I shutdown Tails and wait for the computer to power off 3.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.564
Then Tails is running version 2.3~testoverlayfsng 0.136
And all tps features are active 2.318
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.716
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.081
# 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.315
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.275
When the network is plugged 0.033
And Tor is ready 14.981
Then the Upgrader considers the system as up-to-date 10.834
# 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.536
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.442
After features/support/hooks.rb:291 0.707
After features/support/hooks.rb:75 0.023
29.907
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.615
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.461
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.120
And the signing key used by the Upgrader is outdated 1.588
But a current signing key is available on our website 0.000
When the network is plugged 0.052
And Tor is ready 15.469
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.599
After features/support/hooks.rb:291 0.782
After features/support/hooks.rb:75 0.000