Project Number Date
test_Tails_ISO_stable 4568 13 Dec 2023, 16:02

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 5:51.868 Passed
5:28.861
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.655
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.373
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.408
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.583
When the network is plugged 0.032
And Tor is ready 14.818
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.690
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.105
Given I shutdown Tails and wait for the computer to power off 5.218
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.990
Then Tails is running version 2.2~testoverlayfsng 0.095
And all tps features are active 1.722
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.342
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.284
# 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.031
And Tor is ready 14.189
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.654
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.473
Given I shutdown Tails and wait for the computer to power off 3.066
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.701
Then Tails is running version 2.3~testoverlayfsng 0.096
And all tps features are active 1.634
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.526
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.064
# 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.277
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.291
When the network is plugged 0.025
And Tor is ready 13.290
Then the Upgrader considers the system as up-to-date 0.303
# 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 25.162
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.226
After features/support/hooks.rb:291 0.788
After features/support/hooks.rb:75 0.020
23.007
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 9.141
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.365
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.048
And the signing key used by the Upgrader is outdated 0.443
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 12.440
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.541
After features/support/hooks.rb:291 0.681
After features/support/hooks.rb:75 0.000