Project Number Date
test_Tails_ISO_devel 3235 13 Jan 2024, 12:23

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:16.308 Passed
5:48.899
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.203
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.337
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.059
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.483
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.577
When the network is plugged 0.039
And Tor is ready 20.029
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.679
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.861
Given I shutdown Tails and wait for the computer to power off 5.065
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.268
Then Tails is running version 2.2~testoverlayfsng 0.099
And all tps features are active 2.146
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.338
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.083
# 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.321
When the network is plugged 0.040
And Tor is ready 15.615
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.674
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.327
Given I shutdown Tails and wait for the computer to power off 4.071
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.537
Then Tails is running version 2.3~testoverlayfsng 0.119
And all tps features are active 2.088
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.586
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.282
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.373
When the network is plugged 0.061
And Tor is ready 13.900
Then the Upgrader considers the system as up-to-date 0.338
# 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 27.398
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.395
After features/support/hooks.rb:291 1.006
After features/support/hooks.rb:75 0.025
27.409
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.966
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.294
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.073
And the signing key used by the Upgrader is outdated 0.799
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 13.482
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.755
After features/support/hooks.rb:291 1.018
After features/support/hooks.rb:75 0.000