Project Number Date
test_Tails_ISO_devel 3219 01 Jan 2024, 12:16

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:32.625 Passed
6:4.946
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.076
And no SquashFS delta is installed 0.208
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.532
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.355
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.557
When the network is plugged 0.032
And Tor is ready 16.948
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.884
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.932
Given I shutdown Tails and wait for the computer to power off 9.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.873
Then Tails is running version 2.2~testoverlayfsng 0.165
And all tps features are active 2.620
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.416
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.335
# 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.342
When the network is plugged 0.048
And Tor is ready 19.516
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.634
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.891
Given I shutdown Tails and wait for the computer to power off 4.064
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.355
Then Tails is running version 2.3~testoverlayfsng 0.099
And all tps features are active 2.363
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.633
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.082
# 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.348
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.302
When the network is plugged 0.042
And Tor is ready 14.219
Then the Upgrader considers the system as up-to-date 10.832
# 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.779
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 2.004
After features/support/hooks.rb:291 0.669
After features/support/hooks.rb:75 0.022
27.679
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.829
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.381
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.067
And the signing key used by the Upgrader is outdated 0.931
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 13.456
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.967
After features/support/hooks.rb:291 0.717
After features/support/hooks.rb:75 0.000