Specification

Specification copied to clipboard

Interpreting TAP streams lacking version numbers

13

https://github.com/TestAnything/Specification/pull/25#discussion_r1056428795 Let's pull this into a new issue here :) ----- [eli-schwartz](https://github.com/eli-schwartz) [1 hour ago](https://github.com/TestAnything/Specification/issues/new#discussion_r1056428795) I implemented this in Meson as a passing test which verbosely warns you not to...

isaacs

Hi, I'm interested in possibly developing a ruby parser for TAP, as the only existing library I could find (shown in https://github.com/TestAnything/testanything.github.io/pull/174) is a bit out of date. The [specification,...

ianfixes

Reword to clarify streams lacking a version number

2

See #41 for discussion. Here's my attempt at solving the wording, hopefully even in a manner that technically means the same thing.

eli-schwartz

require test point ID or hyphen-minus when description exists

1

This avoids parsing ambiguity: 1..1 ok 1 is less than 2 Is "1" part of the description, or is it the test point ID? This change makes it clear that...

rhansen

Out of order IDs mixed with missing IDs

6

TAPv14 says: > Test Points _may_ be output in any order, but any Test Point ID provided _must_ be within the range described by the Plan. TAPv14 also says: >...

rhansen

I believe this was an unintentional error; the grammar at the beginning of the specification does include the space.

rhansen

Passing expectedFailure (aka TODO test) should be treated as a failure

1

My problem is with this text (in the “TODO tests” part of the current specification): > Should a todo test point begin succeeding, the harness may report it in some...

mcepl