Project Number Date
test_Tails_ISO_devel 3256 28 Jan 2024, 12:31

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:48.995 Passed
6:19.361
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.877
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.446
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.074
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.403
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.666
When the network is plugged 0.053
And Tor is ready 14.773
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.983
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.937
Given I shutdown Tails and wait for the computer to power off 6.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.509
Then Tails is running version 2.2~testoverlayfsng 0.110
And all tps features are active 2.397
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.439
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.352
# 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.360
When the network is plugged 0.039
And Tor is ready 15.596
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.754
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.258
Given I shutdown Tails and wait for the computer to power off 4.336
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.335
Then Tails is running version 2.3~testoverlayfsng 0.105
And all tps features are active 2.110
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.611
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.073
# 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.304
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.322
When the network is plugged 0.035
And Tor is ready 43.828
Then the Upgrader considers the system as up-to-date 0.264
# 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.023
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.467
After features/support/hooks.rb:291 0.820
After features/support/hooks.rb:75 0.022
29.633
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 10.643
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.056
And the signing key used by the Upgrader is outdated 0.699
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 15.086
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.739
After features/support/hooks.rb:291 0.629
After features/support/hooks.rb:75 0.000