I've created a repository at https://github.com/henryso/gregorio-test
I've created test harnesses for gabc->gregoriotex, gabc->dump, gabc->pdf and tex->pdf. I'm not sure how to do the inclusion and compilation tests, but they should not be too difficult to put in later. I've added some sample tests for illustration. Please review the structure when you have a chance and let me know what I should change. Regards, Henry On Sunday, 15 March 2015 at 08:56:37 pm +0100, Élie Roux wrote: > > > The obviously easiest things to find would be compile problems. As for > > comparing output, the PDFs cannot be compared directly because of the > > creation date and modification date values embedded within the PDF > > itself. I was thinking of using imagemagick to compare, but I still > > have to work that out. > > Indeed, seems like a good idea, but there are always cases where these > tests won't work (a slight change in the spacing algorithm, a change of > shape of one glyph, etc.). Or maybe the best approach would be to have > different test methods, and to decide, test by test, which to use. There > could be > > - gabc->gregoriotex tests, testing the .tex output for some specific > mechanisms > - gabc->dump tests, comparing the dump output for the internal > structure, mainly for gabc syntax tests (for pure gabc, these would be > more accurate than the first ones, as the "dump" output almost never > changes, so tests will be more relevant) > - some gabc->gabc tests, to see if some structures are recognized (not > sure how relevant this would be) > - score inclusion and compilation tests, testing the presence of files > - tex tests testing some annotations, initials, etc. comparing output > with imagemagick > - etc. > > Thank you, > -- > Elie > _______________________________________________ Gregorio-users mailing list [email protected] https://mail.gna.org/listinfo/gregorio-users
