Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What "shape" of data structure can properly hold the results of a parsed TAP log? #45

Open
ianfixes opened this issue Jan 26, 2023 · 0 comments

Comments

@ianfixes
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant