Project Number Date
test_Tails_ISO_devel 3194 14 Dec 2023, 12:11

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 5:47.665 Passed
5:23.760
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 10.154
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.291
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.055
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.398
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.586
When the network is plugged 0.039
And Tor is ready 14.422
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.576
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.660
Given I shutdown Tails and wait for the computer to power off 5.285
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.207
Then Tails is running version 2.2~testoverlayfsng 0.102
And all tps features are active 2.388
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.377
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.276
# 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.274
When the network is plugged 0.034
And Tor is ready 14.485
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.760
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.726
Given I shutdown Tails and wait for the computer to power off 4.275
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.292
Then Tails is running version 2.3~testoverlayfsng 0.098
And all tps features are active 2.060
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.617
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.085
# 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.299
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.340
When the network is plugged 0.043
And Tor is ready 13.895
Then the Upgrader considers the system as up-to-date 0.282
# 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.534
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.664
After features/support/hooks.rb:291 0.746
After features/support/hooks.rb:75 0.021
23.904
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 9.268
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.373
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.056
And the signing key used by the Upgrader is outdated 0.478
But a current signing key is available on our website 0.000
When the network is plugged 0.096
And Tor is ready 11.963
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.667
After features/support/hooks.rb:291 0.646
After features/support/hooks.rb:75 0.000