On 2011.11.16 4:19 PM, James E Keenan wrote: > Should we proceed on the assumption that this specifies v12? > > http://testanything.org/wiki/index.php/TAP_specification > > ... and that this specifies v13? > > http://testanything.org/wiki/index.php/TAP_version_13_specification
No, not for our purposes. YAML diagnostics are not implemented. I thought about it some more, and the v12/v13 split isn't what we're really going for here. Rather than calling it the v12 formatter, it should more properly be called the legacy or TB1 formatter. It's not so much about producing TAP v12 as it is replicating what Test::Builder currently outputs. I can break the issue into two parts. Write a v12 TAP formatter (really v12 this time). This will serve as an easy way to split the formatter into extensible pieces, as all the code currently lies in TAP::v13. This is really straightforward. https://github.com/schwern/test-more/issues/219 Write the legacy formatter as a subclass of TAP::v12. This mostly involves putting the strings TAP uses into attributes and making a subclass of TAP::v12 which changes those defaults. https://github.com/schwern/test-more/issues/215 -- 184. When operating a military vehicle I may *not* attempt something "I saw in a cartoon". -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army http://skippyslist.com/list/
