Project Number Date
test_Tails_ISO_stable 4608 09 Jan 2024, 12:05

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:5.734 Passed
5:37.963
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.060
And no SquashFS delta is installed 0.127
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.358
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.050
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.379
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.495
When the network is plugged 0.053
And Tor is ready 14.626
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.830
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.337
Given I shutdown Tails and wait for the computer to power off 6.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.645
Then Tails is running version 2.2~testoverlayfsng 0.116
And all tps features are active 2.254
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.375
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.308
When the network is plugged 0.044
And Tor is ready 18.647
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.702
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.624
Given I shutdown Tails and wait for the computer to power off 4.113
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.952
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 2.069
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.619
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.076
# 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.278
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.266
When the network is plugged 0.046
And Tor is ready 15.621
Then the Upgrader considers the system as up-to-date 0.277
# 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 24.356
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.466
After features/support/hooks.rb:291 0.759
After features/support/hooks.rb:75 0.061
27.771
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 10.026
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.393
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.062
And the signing key used by the Upgrader is outdated 0.917
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 13.787
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.544
After features/support/hooks.rb:291 0.620
After features/support/hooks.rb:75 0.000