Open thesamesam opened 6 months ago
Good call, I think we'd need, say:
m4
s, including serial changes, missing serial, etc..m4
s that match, some which match when comment-stripped, some new, some serial increment, some serial jump, some identical across the test projects...To avoid sticking binary goo in the repo (for obvious reasons!) do we instead need a make corpus
target that builds the desired git repos locally on the fly prior to make test
?
Ties in the future as well to:
The m4 comparison tools are the most complex and a lot of the time taken when changing things is in making sure we don't break cases.
A simple test suite, maybe just with
diff
on output, to make sure we pick up expected cases would help a lot.