Project Number Date
test_Tails_ISO_stable 4675 20 Feb 2024, 12:19

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:41.289 Passed
6:11.045
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 13.751
And no SquashFS delta is installed 0.151
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.422
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.358
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.566
When the network is plugged 0.041
And Tor is ready 18.143
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.779
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.354
Given I shutdown Tails and wait for the computer to power off 8.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.962
Then Tails is running version 2.2~testoverlayfsng 0.124
And all tps features are active 2.141
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.373
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.286
When the network is plugged 0.047
And Tor is ready 15.162
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.770
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.897
Given I shutdown Tails and wait for the computer to power off 4.494
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.134
Then Tails is running version 2.3~testoverlayfsng 0.100
And all tps features are active 2.098
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.671
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.383
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.324
When the network is plugged 0.043
And Tor is ready 17.320
Then the Upgrader considers the system as up-to-date 0.296
# 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.465
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.494
After features/support/hooks.rb:291 1.195
After features/support/hooks.rb:75 0.022
30.244
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 11.177
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.439
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.075
And the signing key used by the Upgrader is outdated 0.584
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 15.183
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.740
After features/support/hooks.rb:291 0.772
After features/support/hooks.rb:75 0.000