#1 investigate output formats for taskotron
Closed: Fixed Opened by tflink.

One area which needs investigation is the method by which tasks will communicate with the runner. In AutoQA we did most of the output processing in each test and output a log through stdout. We want to take a more structured, scalable approach with taskbt by standardizing output from tasks so that the runner can parse that output easily.

The two choices we're aware of are [[ http://testanything.org/wiki/index.php/Main_Page | TAP ]] and [[ https://launchpad.net/subunit | SubUnit]]. Do an investigation of these two protocols and their supporting libraries. Obviously, the most important language for initial support is Python but we want to support other languages eventually.


As we discussed in https://lists.fedoraproject.org/pipermail/qa-devel/2013-October/000465.html, I believe that TAP (v13) should be the one - it is easily parsable, there already is a TAP producer for Python http://luther.ceplovi.cz/git/bayeux.git/, and I put together (although API needs to be defined) a library for TAPv13 parsing https://bitbucket.org/rajcze/pytap13.

Closing, as TAP is decided on.

Metadata