Specification
Specification copied to clipboard
TestAnything
Working towards a new TAP specification
To make the format have a wider appeal all specific mentions to libraries should be removed from the specification. - Code samples if any are worth keeping should be provided...
As explained by @renormalist in https://github.com/TestAnything/Specification/issues/1#issuecomment-69884266 the ability to extend the YAML format is important for producers and consumers. I suggest we work here on finding the most suitable extendible...
Currently, tests and diagnostics are entirely decoupled from a parsing point of view. The obvious approach of trying to parse a diagnostic after a test line fails is not streaming...
As this is a recurring topic elsewhere this needs it's own issue. This will be a overarching issue for the collective issues (we may break these out into sub issues):...
Create a public roadmap of features/issues to be addressed in each upcoming TAP specification version.
With a new version of TAP brings the ability to make stricter the behaviour around parsing and consuming TAP. I think that (quick notes please feed back): - Implementations should...
To test out future changes to the TAP specification having a set of scripts testing breaking changes on the most common libraries currently using TAP would be worthwhile.
Hi, I am looking at TAP from the point of view of IDE integration. TAP currently defines a way for test runners to report testing results to consumers, hence IDE...
https://github.com/Test-More/test-more/issues/942 Pretty sure in our discussions we decided the Test2 format would be supported formally by TAP14. I have not verified the claims in this ticket yet.
Currently we're only describing the TAP stream and nothing around it. I think it may be useful to also (probably separate from the main document?) to write something about running...