Project Number Date
test_Tails_ISO_devel 3240 17 Jan 2024, 12:37

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:42.152 Passed
5:55.978
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.991
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.300
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.355
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.605
When the network is plugged 0.044
And Tor is ready 17.343
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.879
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.038
Given I shutdown Tails and wait for the computer to power off 6.298
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.263
Then Tails is running version 2.2~testoverlayfsng 0.156
And all tps features are active 2.359
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.403
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.253
# 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.539
When the network is plugged 0.108
And Tor is ready 14.063
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.766
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.460
Given I shutdown Tails and wait for the computer to power off 4.391
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.354
Then Tails is running version 2.3~testoverlayfsng 0.108
And all tps features are active 2.023
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.595
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.068
# 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.311
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.273
When the network is plugged 0.040
And Tor is ready 16.883
Then the Upgrader considers the system as up-to-date 0.280
# 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.048
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.107
After features/support/hooks.rb:291 0.803
After features/support/hooks.rb:75 0.020
46.173
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.599
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.297
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the signing key used by the Upgrader is outdated 0.991
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 33.607
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.581
After features/support/hooks.rb:291 1.138
After features/support/hooks.rb:75 0.000