Project Number Date
test_Tails_ISO_stable 4572 18 Dec 2023, 12:10

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:46.862 Passed
6:18.634
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.293
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.362
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.196
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.497
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.543
When the network is plugged 0.033
And Tor is ready 45.598
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.641
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.259
Given I shutdown Tails and wait for the computer to power off 8.358
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.195
Then Tails is running version 2.2~testoverlayfsng 0.111
And all tps features are active 2.393
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.457
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.341
# 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.318
When the network is plugged 0.051
And Tor is ready 15.991
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.159
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.326
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.859
Then Tails is running version 2.3~testoverlayfsng 0.138
And all tps features are active 2.240
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.777
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.083
# 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.337
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.363
When the network is plugged 0.059
And Tor is ready 14.275
Then the Upgrader considers the system as up-to-date 0.288
# 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 27.315
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.257
After features/support/hooks.rb:291 0.867
After features/support/hooks.rb:75 0.020
28.228
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.247
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.303
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.185
And the signing key used by the Upgrader is outdated 0.658
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 14.950
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.837
After features/support/hooks.rb:291 0.748
After features/support/hooks.rb:75 0.000