I'm afraid I'm not familiar enough with the process of automatic tests
to provide meaningful feedback. For me testing involves compiling a
test score (sometimes more than one) that examines the issue I'm
interested in, looking at the results, and deciding whether they look
like their supposed to. That's part of the reason why I miss so many
things. I often forget about certain use cases when creating my test
scores.
Another thing you might want to look at is completetest.gabc in the
examples folder. This document, if I understand it correctly, is
supposed to test just about every possible combination of gabc syntax,
or at least it did when it was created. It's probably also a good place
to start pulling tests from (you might want to break it up so that it's
easier to tell where the failure is, rather than trying to do everything
at once).
✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝✝
Br. Samuel, OSB
(R. Padraic Springuel)
PAX ☧ ΧΡΙΣΤΟΣ
_______________________________________________
Gregorio-users mailing list
[email protected]
https://mail.gna.org/listinfo/gregorio-users
