|
||||||||
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-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
alex.newn...@shazamteam.com (JIRA) Mon, 26 Nov 2012 03:17:49 -0800
- [JIRA] (JENKINS-15322) NOTESTS in TAP r... brunodepau...@yahoo.com.br (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... brunodepau...@yahoo.com.br (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... brunodepau...@yahoo.com.br (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... brunodepau...@yahoo.com.br (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... brunodepau...@yahoo.com.br (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... alex.newn...@shazamteam.com (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... alex.newn...@shazamteam.com (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... brunodepau...@yahoo.com.br (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... alex.newn...@shazamteam.com (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... brunodepau...@yahoo.com.br (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... brunodepau...@yahoo.com.br (JIRA)
- [JIRA] (JENKINS-15322) NOTESTS in ... alex.newn...@shazamteam.com (JIRA)
Thanks for the update
We are parsing our .t files via TAP::Harness using Test::Harness v3.25 which states it's output is TAP version 12. Perhaps there's a mismatch here somewhere between the TAP produced by our Test::More module and Tap::Harness and the TAP specifications. Or maybe the plugin is expecting a different TAP version?
Currently I can't investigate further as http://testanything.org is down at the moment.
In our projects we can't easily switch to using prove from the command line or a bash script as our .t files aren't static, they rely on a whole bunch of variable being passed into them via the TAP::Harness, there may be other workarounds possible though.