Project Number Date
test_Tails_ISO_stable 4662 12 Feb 2024, 14:52

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:16.368 Passed
5:48.582
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.508
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.315
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.075
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.402
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.547
When the network is plugged 0.029
And Tor is ready 18.380
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.702
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.344
Given I shutdown Tails and wait for the computer to power off 6.485
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.582
Then Tails is running version 2.2~testoverlayfsng 0.112
And all tps features are active 1.732
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.374
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.331
When the network is plugged 0.021
And Tor is ready 14.834
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.509
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.890
Given I shutdown Tails and wait for the computer to power off 4.448
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.337
Then Tails is running version 2.3~testoverlayfsng 0.117
And all tps features are active 1.681
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.631
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.062
# 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.284
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.301
When the network is plugged 0.022
And Tor is ready 14.881
Then the Upgrader considers the system as up-to-date 0.287
# 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.381
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.432
After features/support/hooks.rb:291 0.746
After features/support/hooks.rb:75 0.024
27.785
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.713
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.309
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.063
And the signing key used by the Upgrader is outdated 1.300
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 13.645
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.699
After features/support/hooks.rb:291 0.704
After features/support/hooks.rb:75 0.000