Project Number Date
test_Tails_ISO_stable 4562 11 Dec 2023, 12:15

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:33.931 Passed
6:4.925
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 10.297
And no SquashFS delta is installed 0.148
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.347
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.122
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.437
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.667
When the network is plugged 0.043
And Tor is ready 18.656
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.826
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.145
Given I shutdown Tails and wait for the computer to power off 6.300
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.871
Then Tails is running version 2.2~testoverlayfsng 0.156
And all tps features are active 5.010
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.453
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.407
When the network is plugged 0.240
And Tor is ready 18.560
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.740
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.077
Given I shutdown Tails and wait for the computer to power off 5.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.143
Then Tails is running version 2.3~testoverlayfsng 0.158
And all tps features are active 2.478
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.627
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.094
# 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.297
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.411
When the network is plugged 0.036
And Tor is ready 18.672
Then the Upgrader considers the system as up-to-date 0.289
# 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.681
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.748
After features/support/hooks.rb:291 0.773
After features/support/hooks.rb:75 0.037
29.006
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 10.052
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.349
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the signing key used by the Upgrader is outdated 0.698
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 16.139
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.661
After features/support/hooks.rb:291 1.195
After features/support/hooks.rb:75 0.000