Project Number Date
test_Tails_ISO_stable 4604 07 Jan 2024, 12:32

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:37.757 Passed
6:8.186
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.286
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.371
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.070
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.377
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.635
When the network is plugged 0.036
And Tor is ready 18.684
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.944
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.901
Given I shutdown Tails and wait for the computer to power off 6.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.200
Then Tails is running version 2.2~testoverlayfsng 0.140
And all tps features are active 2.233
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.471
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.092
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.285
# 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.344
When the network is plugged 0.054
And Tor is ready 19.119
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.205
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.686
Given I shutdown Tails and wait for the computer to power off 4.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.166
Then Tails is running version 2.3~testoverlayfsng 0.122
And all tps features are active 2.223
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.639
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.106
# 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.334
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.352
When the network is plugged 0.049
And Tor is ready 16.409
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 26.848
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.675
After features/support/hooks.rb:291 0.904
After features/support/hooks.rb:75 0.020
29.570
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 9.373
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.353
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.079
And the signing key used by the Upgrader is outdated 1.528
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 16.444
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.694
After features/support/hooks.rb:291 1.272
After features/support/hooks.rb:75 0.000