Project Number Date
test_Tails_ISO_devel 3202 20 Dec 2023, 12:36

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:59.695 Passed
6:32.096
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.494
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.271
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.082
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.436
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.571
When the network is plugged 0.050
And Tor is ready 16.966
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.695
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.204
Given I shutdown Tails and wait for the computer to power off 6.230
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.674
Then Tails is running version 2.2~testoverlayfsng 0.128
And all tps features are active 2.386
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.444
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.276
When the network is plugged 0.043
And Tor is ready 16.404
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.913
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.027
Given I shutdown Tails and wait for the computer to power off 4.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.297
Then Tails is running version 2.3~testoverlayfsng 0.103
And all tps features are active 2.086
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.647
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.075
# 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.299
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.374
When the network is plugged 0.049
And Tor is ready 42.830
Then the Upgrader considers the system as up-to-date 0.275
# 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.657
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.202
After features/support/hooks.rb:291 0.794
After features/support/hooks.rb:75 0.026
27.598
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 10.789
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.116
And the signing key used by the Upgrader is outdated 0.491
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 12.985
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.867
After features/support/hooks.rb:291 0.753
After features/support/hooks.rb:75 0.000