Project Number Date
test_Tails_ISO_stable 4576 18 Dec 2023, 22:11

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:8.885 Passed
5:42.301
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.954
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.395
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.079
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.380
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.575
When the network is plugged 0.043
And Tor is ready 18.933
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.584
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.992
Given I shutdown Tails and wait for the computer to power off 6.190
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.892
Then Tails is running version 2.2~testoverlayfsng 0.084
And all tps features are active 2.245
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.367
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.272
# 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.279
When the network is plugged 0.044
And Tor is ready 17.381
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.547
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.069
Given I shutdown Tails and wait for the computer to power off 4.076
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.872
Then Tails is running version 2.3~testoverlayfsng 0.095
And all tps features are active 2.266
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.585
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.071
# 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.269
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.285
When the network is plugged 0.052
And Tor is ready 14.869
Then the Upgrader considers the system as up-to-date 0.263
# 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 24.649
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.479
After features/support/hooks.rb:291 0.806
After features/support/hooks.rb:75 0.018
26.584
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.630
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.447
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.081
And the signing key used by the Upgrader is outdated 0.699
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 13.093
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.593
After features/support/hooks.rb:291 0.838
After features/support/hooks.rb:75 0.000