I happened to come across these recently which might not have existed when the mx corpus was being developed initially:
https://github.com/cuthbertLab/musicxmlTestSuite
However I noticed when looking at it that the tests were derived from another suite which I believe we do have in the corpus.
The important point is that we should analyze the test suite and only add files that are novel and actually add real coverage beyond what our test corpus already covers. Adding tests slows down the run and increases the repo size, so they should only be added when they are covering MusicXML structures otherwise novel to the existing corpus.
The same work should be done for the test suite that the MusicXML repo's own test corpus. I don't think that existed either when mx created its corpus.
I happened to come across these recently which might not have existed when the mx corpus was being developed initially:
https://github.com/cuthbertLab/musicxmlTestSuite
However I noticed when looking at it that the tests were derived from another suite which I believe we do have in the corpus.
The important point is that we should analyze the test suite and only add files that are novel and actually add real coverage beyond what our test corpus already covers. Adding tests slows down the run and increases the repo size, so they should only be added when they are covering MusicXML structures otherwise novel to the existing corpus.
The same work should be done for the test suite that the MusicXML repo's own test corpus. I don't think that existed either when mx created its corpus.