Soham <soh...@loveyaml.org> writes: > Well, I forgot to clarify in the original email, but my particular > target use-case is is "unit tests" written in code, say for a particular > function or class. In that case it gets cumbersome to have one binary > per test (atleast IMO). My idea is to add support for a TAP output like > so:
> [not] ok 5 - Call sys_open with negative file descriptor # XFAIL For what it's worth, TODO really is the way that you're supposed to express this in the TAP protocol. Tests that are expected to fail and should be reported as an unexpected outcome if they pass are suppoesd to be marked with "TODO". See https://testanything.org/tap-specification.html under "TODO tests". Please don't take this as opposition to your proposal -- Automake should feel free to do anything that works for Automake since I'm not sure how much interoperability between different TAP harnesses matters -- but strictly speaking there is a way to achieve what I think you want within the TAP protocol without extensions. -- Russ Allbery (ea...@eyrie.org) <https://www.eyrie.org/~eagle/>
