Project Number Date
test_Tails_ISO_stable 4669 16 Feb 2024, 19: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:33.790 Passed
6:8.365
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 10.832
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.303
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.084
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.412
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.537
When the network is plugged 0.020
And Tor is ready 16.159
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.662
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.791
Given I shutdown Tails and wait for the computer to power off 5.068
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.711
Then Tails is running version 2.2~testoverlayfsng 0.111
And all tps features are active 1.732
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.427
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.282
# 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.320
When the network is plugged 0.026
And Tor is ready 16.585
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.794
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.125
Given I shutdown Tails and wait for the computer to power off 4.073
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.925
Then Tails is running version 2.3~testoverlayfsng 0.113
And all tps features are active 1.687
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.566
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.064
# 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.295
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.311
When the network is plugged 0.054
And Tor is ready 42.968
Then the Upgrader considers the system as up-to-date 0.289
# 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 25.242
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.574
After features/support/hooks.rb:291 0.824
After features/support/hooks.rb:75 0.035
25.424
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 8.989
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.338
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.086
And the signing key used by the Upgrader is outdated 0.569
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 13.737
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.652
After features/support/hooks.rb:291 0.636
After features/support/hooks.rb:75 0.000