Project Number Date
test_Tails_ISO_stable 4574 18 Dec 2023, 15:29

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:32.395 Passed
6:4.542
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 11.890
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.390
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.069
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.482
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.599
When the network is plugged 0.063
And Tor is ready 20.279
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.731
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.404
Given I shutdown Tails and wait for the computer to power off 6.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.342
Then Tails is running version 2.2~testoverlayfsng 0.107
And all tps features are active 2.299
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.420
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.316
When the network is plugged 0.073
And Tor is ready 14.707
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.731
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.873
Given I shutdown Tails and wait for the computer to power off 4.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.640
Then Tails is running version 2.3~testoverlayfsng 0.114
And all tps features are active 2.253
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.639
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.073
# 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.322
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.354
When the network is plugged 0.040
And Tor is ready 17.120
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.965
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.538
After features/support/hooks.rb:291 1.032
After features/support/hooks.rb:75 0.023
27.852
Before features/support/hooks.rb:245 0.008
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.435
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.051
And the signing key used by the Upgrader is outdated 1.263
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 13.369
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.725
After features/support/hooks.rb:291 0.871
After features/support/hooks.rb:75 0.000