I've added to TAP::Parser an experimental YAML syntax for embedding
machine readable diagnostic information in TAP streams. The syntax looks
like this:
1..5
ok 1
ok 2
---
-
fnurk: skib
ponk: gleeb
-
bar: krup
foo: plink
...
ok 3
ok 4
---
expected:
- 1
- 2
- 4
got:
- 1
- pong
- 4
...
ok 5
I'm not actually doing anything with the YAML blocks yet but the parser
handles them correctly. I'm open to suggestions for what we do with the
data now we have it :)
The YAML parser we're currently using needs to be fed an entire YAML
document in a string so the parser has to recognise the boundaries of
the YAML and only then pass it to the parser. This means that if the
trailing '...' is missing the whole of the remainder of the TAP stream
will be consumed. I'll probably modify the YAML parser so that it reads
directly from the TAP stream.
If anyone's interested you can get it from the SVN:.
http://svn.hexten.net/tapx
--
Andy Armstrong, hexten.net
