Project Number Date
test_Tails_ISO_devel 3251 25 Jan 2024, 00:33

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:28.728 Passed
6:1.520
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.095
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.277
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.071
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.428
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.611
When the network is plugged 0.043
And Tor is ready 17.853
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.683
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.515
Given I shutdown Tails and wait for the computer to power off 6.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.349
Then Tails is running version 2.2~testoverlayfsng 0.144
And all tps features are active 2.339
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.501
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.112
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.322
# 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.281
When the network is plugged 0.044
And Tor is ready 16.928
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.904
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.986
Given I shutdown Tails and wait for the computer to power off 4.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.334
Then Tails is running version 2.3~testoverlayfsng 0.096
And all tps features are active 2.461
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.675
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.091
# 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.271
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.326
When the network is plugged 0.043
And Tor is ready 16.052
Then the Upgrader considers the system as up-to-date 0.286
# 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.525
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.175
After features/support/hooks.rb:291 0.746
After features/support/hooks.rb:75 0.024
27.208
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.714
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.403
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.062
And the signing key used by the Upgrader is outdated 0.548
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 13.877
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.563
After features/support/hooks.rb:291 0.642
After features/support/hooks.rb:75 0.000