Project Number Date
test_Tails_ISO_devel 3193 13 Dec 2023, 16:53

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:21.752 Passed
5:27.589
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.028
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.284
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.070
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.466
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.473
When the network is plugged 0.063
And Tor is ready 16.452
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.637
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.743
Given I shutdown Tails and wait for the computer to power off 5.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.516
Then Tails is running version 2.2~testoverlayfsng 0.089
And all tps features are active 2.104
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.407
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.329
# 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.305
When the network is plugged 0.019
And Tor is ready 13.178
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.675
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.734
Given I shutdown Tails and wait for the computer to power off 3.192
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.047
Then Tails is running version 2.3~testoverlayfsng 0.101
And all tps features are active 1.730
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.563
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.110
# 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.275
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.313
When the network is plugged 0.037
And Tor is ready 15.647
Then the Upgrader considers the system as up-to-date 0.309
# 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.006
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.207
After features/support/hooks.rb:291 0.742
After features/support/hooks.rb:75 0.021
54.163
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.765
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.297
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.087
And the signing key used by the Upgrader is outdated 0.463
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 42.946
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.571
After features/support/hooks.rb:291 0.647
After features/support/hooks.rb:75 0.000