qt6-bb10/qtsvg/tests/manual/rendertestsuite
BB10 Port 0d2227012e Add Qt6 module sources (svg, shadertools, declarative, httpserver, multimedia)
Consolidate the BB10 Qt module sources into this repo alongside qtbase so the
full Qt6 cross-build is reproducible from one place (previously separate,
unpushed sibling repos that could be lost). v6.8.3 + BB10 patches:
- qtshadertools: SPIRV-Cross langinfo guard for QNX.
- qtmultimedia: drop QNX audio backend block.
- qtsvg/qtdeclarative/qthttpserver: pristine (no source patches needed).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-23 01:14:15 +02:00
..
README Add Qt6 module sources (svg, shadertools, declarative, httpserver, multimedia) 2026-06-23 01:14:15 +02:00
main.cpp Add Qt6 module sources (svg, shadertools, declarative, httpserver, multimedia) 2026-06-23 01:14:15 +02:00
rendertestsuite.pro Add Qt6 module sources (svg, shadertools, declarative, httpserver, multimedia) 2026-06-23 01:14:15 +02:00

README

This little helper program can be used together with the SVG Tiny 1.2 test
suite to determine the visual impact of changes to the renderer on the basis of
the test suite.

Suppose you have the test suite installed in ~/tests, then you can create a
base line of renderings of all the SVG images by running

    mkdir baseline
    ./rendertestsuite create-baseline ~/tests

and the output will be stored in the 'baseline/' sub-directory.

After making changes to the renderer, you can create a new set of images by running

    mkdir difference
    ./rendertestsuite diff ~/tests

and side-by-side images of the old and the new images in case they differ will
be stored in the sub-directory 'difference/'.

An easy way to inspect the output is by using KDE's gwenview:

    gwenview difference/


Note that due to rounding errors there will always be subtle differences, even
when not doing any changes to the renderer.


You can find the test suite at

    https://www.w3.org/Graphics/SVG/WG/wiki/Test_Suite_Overview#SVG_1.2_Tiny_Test_Suite:_12_September_2008