Project Number Date
test_Tails_ISO_stable 4680 24 Feb 2024, 12:22

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:23.518 Passed
5:56.397
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.718
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.372
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.052
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.349
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.594
When the network is plugged 0.060
And Tor is ready 17.460
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.758
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.542
Given I shutdown Tails and wait for the computer to power off 6.366
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.626
Then Tails is running version 2.2~testoverlayfsng 0.118
And all tps features are active 2.341
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.359
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.276
# 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.290
When the network is plugged 0.055
And Tor is ready 17.598
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.620
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.915
Given I shutdown Tails and wait for the computer to power off 4.302
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.624
Then Tails is running version 2.3~testoverlayfsng 0.127
And all tps features are active 2.360
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.583
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.071
# 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.276
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.319
When the network is plugged 0.042
And Tor is ready 15.089
Then the Upgrader considers the system as up-to-date 0.311
# 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 29.201
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.448
After features/support/hooks.rb:291 0.797
After features/support/hooks.rb:75 0.027
27.121
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 10.566
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.342
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the signing key used by the Upgrader is outdated 0.669
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 12.521
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.906
After features/support/hooks.rb:291 0.687
After features/support/hooks.rb:75 0.000