Project Number Date
test_Tails_ISO_stable 4620 16 Jan 2024, 12:09

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:42.237 Passed
6:12.995
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.616
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.323
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.091
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.370
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.546
When the network is plugged 0.065
And Tor is ready 18.528
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.781
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.165
Given I shutdown Tails and wait for the computer to power off 5.329
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.626
Then Tails is running version 2.2~testoverlayfsng 0.100
And all tps features are active 2.378
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.445
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.290
# 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.277
When the network is plugged 0.032
And Tor is ready 13.626
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.681
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.724
Given I shutdown Tails and wait for the computer to power off 3.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.434
Then Tails is running version 2.3~testoverlayfsng 0.140
And all tps features are active 2.086
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.057
# 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.297
When the network is plugged 0.037
And Tor is ready 42.096
Then the Upgrader considers the system as up-to-date 0.293
# 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 30.270
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.610
After features/support/hooks.rb:291 0.739
After features/support/hooks.rb:75 0.023
29.241
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 9.424
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.312
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.076
And the signing key used by the Upgrader is outdated 1.178
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 15.385
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.808
After features/support/hooks.rb:291 0.602
After features/support/hooks.rb:75 0.000