|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-16325) TAP Parser can't ... [email protected] (JIRA)
- [JIRA] (JENKINS-16325) TAP Parser c... [email protected] (JIRA)
- [JIRA] (JENKINS-16325) TAP Parser c... [email protected] (JIRA)
- [JIRA] (JENKINS-16325) TAP Parser c... [email protected] (JIRA)
- [JIRA] (JENKINS-16325) TAP Parser c... [email protected] (JIRA)
- [JIRA] (JENKINS-16325) TAP Parser c... [email protected] (JIRA)

Hi again Todd :o)
You are not the first one to complain about the TAP plug-in not being fully compliant with Perl's test tools
When I wrote the plug-in I was focused in using it for TAP with Java (mainly using Selenium + TestNG outputting TAP with attachments [yamlish]).
Could you send or attach an example, please (take care with private or confidential data in your attachments as it takes a while to delete an attachment in JIRA)?
tap4j probably can't handle prove's output... but maybe we could create a new parser in tap plug-in, that would pre-parse prove output and then use tap4j parsers to get the TAP information. What do you think?
In order to keep backward compatibility, that would be a new option in the plug-in job configuration section, and not enabled by default (i.e. a new unchecked check box with a title like "Parse prove output").
Thanks for filing this issue. I'm using more Perl at work now, so maybe we can fix this issue and I'll learn more about prove and other Perl utilities.
/B