Project Number Date
test_Tails_ISO_devel 3253 25 Jan 2024, 22:07

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:19.942 Passed
5:54.369
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.767
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.266
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.115
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.425
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.492
When the network is plugged 0.025
And Tor is ready 15.526
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.707
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.553
Given I shutdown Tails and wait for the computer to power off 7.386
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.661
Then Tails is running version 2.2~testoverlayfsng 0.131
And all tps features are active 2.019
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.366
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.310
# 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.307
When the network is plugged 0.030
And Tor is ready 15.496
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.783
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.664
Given I shutdown Tails and wait for the computer to power off 4.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.762
Then Tails is running version 2.3~testoverlayfsng 0.125
And all tps features are active 2.052
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.664
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.092
# 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.289
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.301
When the network is plugged 0.043
And Tor is ready 15.397
Then the Upgrader considers the system as up-to-date 0.342
# 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 29.149
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.692
After features/support/hooks.rb:291 0.754
After features/support/hooks.rb:75 0.023
25.573
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 8.989
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.350
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.068
And the signing key used by the Upgrader is outdated 1.123
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 13.432
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.590
After features/support/hooks.rb:291 0.670
After features/support/hooks.rb:75 0.000