Project Number Date
test_Tails_ISO_stable 4616 12 Jan 2024, 12:20

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:30.269 Passed
5:57.409
Before features/support/hooks.rb:245 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.813
And no SquashFS delta is installed 0.131
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.306
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.050
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.370
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.587
When the network is plugged 0.037
And Tor is ready 18.835
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.686
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.184
Given I shutdown Tails and wait for the computer to power off 5.221
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.846
Then Tails is running version 2.2~testoverlayfsng 0.114
And all tps features are active 2.288
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.406
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.308
# 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.326
When the network is plugged 0.042
And Tor is ready 15.159
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.605
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.252
Given I shutdown Tails and wait for the computer to power off 3.155
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.589
Then Tails is running version 2.3~testoverlayfsng 0.125
And all tps features are active 2.140
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.532
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.055
# 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.280
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.409
When the network is plugged 0.108
And Tor is ready 15.962
Then the Upgrader considers the system as up-to-date 0.272
# 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 24.814
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.324
After features/support/hooks.rb:291 0.802
After features/support/hooks.rb:75 0.021
32.859
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 11.066
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.307
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.066
And the signing key used by the Upgrader is outdated 1.552
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 17.198
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.615
After features/support/hooks.rb:291 1.111
After features/support/hooks.rb:75 0.000