Project Number Date
test_Tails_ISO_devel 3216 29 Dec 2023, 12:15

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:29.753 Passed
6:2.725
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 11.415
And no SquashFS delta is installed 0.159
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.374
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.108
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.414
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.661
When the network is plugged 0.040
And Tor is ready 18.112
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.763
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 11.007
Given I shutdown Tails and wait for the computer to power off 8.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.750
Then Tails is running version 2.2~testoverlayfsng 0.103
And all tps features are active 2.413
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.399
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.269
# 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.385
When the network is plugged 0.046
And Tor is ready 15.967
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.663
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 3.373
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.810
Then Tails is running version 2.3~testoverlayfsng 0.099
And all tps features are active 2.210
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.640
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.078
# 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.294
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.327
When the network is plugged 0.036
And Tor is ready 16.120
Then the Upgrader considers the system as up-to-date 0.382
# 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 30.579
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.309
After features/support/hooks.rb:291 0.767
After features/support/hooks.rb:75 0.019
27.028
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 9.972
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.355
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the signing key used by the Upgrader is outdated 0.502
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 12.429
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.661
After features/support/hooks.rb:291 0.732
After features/support/hooks.rb:75 0.000