On 9 October 2013 06:46, Tavmjong Bah <tavmjong@...8...> wrote:
+1, I wasn't aware that there was testing being done other than that the compilation was successful.
Actually, yes, the PPA package builder runs "make check" at the end of each compilation and reports a build-failure if any of the tests fail (or if known-failures succeed). At the moment, "make check" runs the following:
1. C++ unit tests, using cxxtest. (Some of these are known failures that need fixing) 2. Unit tests on the extension scripts 3. A translations test
If the automated SVG compliance tests are added to the "TESTS" list in src/Makefile.am, then the PPA builder will take care of it.
As for seeing the test output, I think that should also be fairly straightforward. We'd just need to install the images that are generated in the PPA build into a new binary target called something like "inkscape-trunk-svg-test-results".
This will all then result in completely "hands-free" testing whenever trunk is updated. For best results, we should really try to separate the SVG tests into known-success and known-failure lists that can be put into separate good/bad lists for "make check". The automated builder will then complain at us whenever our SVG compliance level changes.
AV