@James, thanks, I'll take a look on it in the next days. Probably it's a bug in tap4j.
Thanks for attaching the exception and a sample tap stream
Bruno P. Kinoshita
added a comment - @James, thanks, I'll take a look on it in the next days. Probably it's a bug in tap4j.
Thanks for attaching the exception and a sample tap stream
Bruno P. Kinoshita
added a comment - Confirmed it's a bug in tap4j [1] . Already fixed, cutting a new release.
Will bump up the tap4j dependency version and will test again to see if the exception is gone.
[1] https://github.com/tupilabs/tap4j/issues/12
SCM/JIRA link daemon
added a comment - Code changed in jenkins
User: Bruno P. Kinoshita
Path:
pom.xml
http://jenkins-ci.org/commit/tap-plugin/3823b83e9fa2ae249a0cadcdbb936291c1c2781f
Log:
[FIXED JENKINS-17947] Nested TAP not parsed correctly
However, the subtests are not being included in the table of TAP tests. I'll take a look, since there are other issues related to enhancing the information displayed in the TAP tests table.
Thanks in advance!
Bruno
Bruno P. Kinoshita
added a comment - Just tested locally, seems to be working now.
However, the subtests are not being included in the table of TAP tests. I'll take a look, since there are other issues related to enhancing the information displayed in the TAP tests table.
Thanks in advance!
Bruno
> However, the subtests are not being included in the table of TAP tests.
Is that fixed in 1.11, or is that for another ticket?
James Howe
added a comment - > However, the subtests are not being included in the table of TAP tests.
Is that fixed in 1.11, or is that for another ticket?
Ops, my bad, I forgot to mention what had been fixed in this 1.11. We've fixed only the TAP parsing issue.
Could you file a new one really. No need to get into details, just say that it's not including subtests. I'll make this new issue sub-issue of another issue I'm working on to enhance the plug-in UI.
Bruno P. Kinoshita
added a comment - Hi James!
Ops, my bad, I forgot to mention what had been fixed in this 1.11. We've fixed only the TAP parsing issue.
Could you file a new one really. No need to get into details, just say that it's not including subtests. I'll make this new issue sub-issue of another issue I'm working on to enhance the plug-in UI.
If the first test has no subtests then parsing completes, but then none of the subtests appear in the results.