| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Leaks from libfontconfig.so are excluded for now, as it doesn't seem to
be our fault. The gcc mechanism to suppress leaks doesn't seem to be
working, so we fallback to awk.
In the presence of leaks, that specific test will fail by returning
non-zero, but this will not be what we want for those tests that are
currently failing with XPASS. We will only consider the ones that are
passing as those targeted for leak detection.
|
|
Newer versions output two numbers instead of just one, so we pick the
first number:
++ compare -metric AE b-div.html_wdir/{html.png,ref.png,diff.png}
+ diffcount='0 (0)'
+ '[' '0 (0)' = 0 ']'
+ echo FAIL
FAIL
|
|
Use the environment variable DILLO_TEST_WAIT_TIME to lower the default
time to wait since dillo window appears and when we take the screenshot
to compare the rendering output.
|
|
|
|
|
|
This suppresses a warning on more modern systems while preserving
the ability of older systems and CI/CD to run the test suite.
> WARNING: The convert command is deprecated in IMv7, \
> use "magick" instead of "convert" or "magick convert"
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
As we run the driver with "set -e", it will stop on the first failure.
The compare(1) command from magick exits with non-zero when the inputs
are not equal:
> The compare program returns 2 on error, 0 if the images are similar,
> or a value between 0 and 1 if they are not similar.
So, to prevent it from interrupting the cleanup steps after the
comparison, we make it always success.
|
|
In order to leave a clean build directory by distclean, all generated
files must be removed. The environment variable DILLO_TEST_LEAVE_FILES
can be set to leave the generated test results, which aids debugging
when tests fail.
|
|
These tests render a HTML page in Dillo and save a screenshot which is
compared with another one rendered by a reference HTML file which
doesn't make use of the feature under test.
Running these tests require some additional dependencies to run a Xorg
server and capture screenshots of the browser, so they are only enabled
when configured with the --enable-html-tests option.
Additionally, running Dillo and opening local files requires a working
file dpi plugin. So, when running the HTML tests it is required that a
working dpid server can be launched by Dillo. To do so, Dillo can be
first installed to a prefix directory, the dpidrc file copied to
~/.dillo/ and then the DILLOBIN variable set to the path of the dillo
binary under test.
|
