10 Oct
2013
10 Oct
'13
3:02 p.m.
On Thu, 2013-10-10 at 15:12 +0100, Alex Valavanis wrote:
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.
Looking at the structure of our svg tests, they do appear to have good and bad result directories. Known bad is just a matter of filling the specific directory with specifically named files and likewise known good.
Martin,