J.B.C.Engelen@...1578... wrote:
** If there is someone out there who likes to make website stuff, please help with our test suite ! ** ... Perhaps there is a program that gives a measure of how equal images are, instead of simply "equal"/"not equal"? It would be very nice if the system didn't need much user intervention, or if that intervention would be very easy. (e.g. website based)
During the time I did it I only had to rejudge images occasionally, and you only have to look at the output image and move it to either the pass or the fail references (and then commit). But yes, it would be great to have a web interface for this, especially for users who are unfamiliar with SVN.
... You know I am a big fan of the testsuite, but for some reason, there are very few people using it. IMHO it would be much better if people would add testfiles to the testsuite instead of adding them to the bugtracker, but it doesn't happen.
Indeed, I greatly appreciate the effort you've put into making new
Perhaps clearifying the result listing can help. I don't know...
The Wiki is currently down so I can't check the exact URL (probably just http://www.inkscape.org/wiki/index.php/TestingInkscape as linked to from the testsuite result page), but there is quite a bit of documentation on the Wiki on testing Inkscape (both unit tests and rendering tests). In short:
Inkscape has unit tests to (mostly) test low-level functionality which are run using make check (or the Windows equivalent) and implemented in code using CxxTest.
In addition Inkscape has rendering tests to test high level functionality. These tests are run using runtests.py in the test repository (in Inkscape's SVN) and consist of a test SVG and references PNGs. For each test there can be any number of fail and/or pass references to which the test program tries to match the output. As Inkscape's output doesn't change too often this makes it relatively easy to keep up with any changes that do occur manually. Especially when combined with perceptualdiff to filter out really trivial changes.
Also, instead of a pass reference another SVG file (called a patch file) can be given which Inkscape should render in exactly the same way but which IS rendered correctly. This can make comparisons slightly more robust and enables a pass reference to be made before Inkscape actually passes a test.