[ 
https://issues.jenkins-ci.org/browse/JENKINS-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160188#comment-160188
 ] 

Bruno P. Kinoshita commented on JENKINS-13037:
----------------------------------------------

Hi Bogdan, 

> I can't help you with that, but you can tell me what you need from it and i 
> will help.

No worries, I had few hypothesis on my mind :-)

Are you using JUnit to generate this XML? Which version? 

I can see on <testsuite> there is an error. Probably there are 4 <testcase>'s 
in this XML too. The one that failed. Does it contain an error attribute? An 
error element? Does it contain any text? This is important to know, as I'm 
using Jenkins own JUnit parser.

> Can you please remove the screenshot now?

I'm afraid only JIRA administrators can do that. If you need that done, 
probably the best idea is go to #jenkins IRC channel on FreeNode and talk to 
one of the guys with admin karma.

Bruno
                
> TestLink Plugin with jUnit
> --------------------------
>
>                 Key: JENKINS-13037
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13037
>             Project: Jenkins
>          Issue Type: Bug
>          Components: testlink
>    Affects Versions: current
>         Environment: Ubuntu 10.04
>            Reporter: Bogdan Girbea
>            Assignee: Bruno P. Kinoshita
>              Labels: jenkins
>         Attachments: Screenshot.png
>
>
> Hello
> I am using the 3.1 testlink plugin. I am running a test class, with 4 tests 
> using JUnit 4.8.One of the 4 tests throws an error and still the testlink 
> report marks the test class as passed.
> If needed i can attach the configurations and/or the results.. 
> Thank you!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to