As a followup to Bruce’s suggestion of standard test suites, I’m
attaching a proposal for a file hierarchy and layouts for item data
and attribute/element tests. In the sample test files, I’ve meant to
model the item keys on what’s used by citeproc-hs, but I haven’t used
the tool itself, so please correct that if I’ve gotten that wrong.
A processor undergoing testing would need to parse these files and
compose them into its own test-suite syntax. People setting tests for
the specification shouldn’t need to worry about any of that, so I’ve
tried to keep the syntax to a minimum.
It should be obvious how the files would be parsed. If it’s not, the
layout can be changed in any way people feel comfortable with. I’m
hoping this will be easily accessible; contributions from Bruce and
Elena and others active in the design of the language would be of