Project Number Date
test_Tails_ISO_stable 4656 08 Feb 2024, 13:03

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:31.913 Passed
6:2.521
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 11.070
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.453
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.076
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.445
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.639
When the network is plugged 0.041
And Tor is ready 17.732
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.858
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.563
Given I shutdown Tails and wait for the computer to power off 5.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.088
Then Tails is running version 2.2~testoverlayfsng 0.122
And all tps features are active 2.231
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.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.295
# 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.313
When the network is plugged 0.033
And Tor is ready 15.570
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.075
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.670
Given I shutdown Tails and wait for the computer to power off 4.276
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.376
Then Tails is running version 2.3~testoverlayfsng 0.125
And all tps features are active 2.357
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.570
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.100
# 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.349
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.348
When the network is plugged 0.038
And Tor is ready 16.554
Then the Upgrader considers the system as up-to-date 0.462
# 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.357
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.507
After features/support/hooks.rb:291 0.866
After features/support/hooks.rb:75 0.019
29.392
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.096
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.460
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.098
And the signing key used by the Upgrader is outdated 0.645
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 16.324
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.715
After features/support/hooks.rb:291 0.974
After features/support/hooks.rb:75 0.000