What "shape" of data structure can properly hold the results of a parsed TAP log? #45
Description
Hi, I'm interested in possibly developing a ruby parser for TAP, as the only existing library I could find (shown in TestAnything/testanything.github.io#174) is a bit out of date.
The specification, version 14 is informative, but in terms of parsing I'm not sure what the equivalent data structure should look like. For example, it seems like outside of each listing of test cases there is a "meta" test being made of whether the number of executed tests matches the number of declared tests. For a given test, they can be marked as skipped / TODO with a message field, or complete successfully, or fail with some structured output. But I'm having trouble seeing the big picture amidst the low-level parsing rules.
Do you have an example in JSON or YAML that directly translates to TAP and back again? Am I missing something?