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

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

Hi Vignesh!

>For me both the names of the Test suite name and the class name is the same, 
>this i found out by looking at the junit report it showed me the same name.

I believe this issue is occurring for this reason :) At moment I'm working on a 
new release that will let you choose between one/or many test result seeking 
strategies. I.e., you'll be able to configure "For this Job, you have to seek 
JUnit results using certain pattern to locate files, and match the key custom 
field with the *JUnit Suite Name*".

All the strategies are very similar, except by the last term, surrounded by 
*'s. At moment, I've created the following strategies (the name tells what I'm 
using to match against the key custom field value): 

- JUnit suite name
- JUnit test name
- JUnit test class name
- TestNG suite name
- TestNG class name
- TestNG package.class#method name (com.sample.TestA#testVoid)
- TAP file name

And for a future release, I plan to include: 

- JUnit Xpath expression (this way, you'll can say something like: match the 
key custom field value against suite[name=LocatorsTests*])
- TAP YAMLish field

However, it would be great if you could attach a sample test project that 
produces similar output. Comments or suggestions on these new strategies are 
very welcome too! I'll try to cut a release before March, and if you have some 
spare time to test an alpha version, maybe you could test the plug-in and say 
if this new version works for your issue ;) 

Cheers, B
                
> JUnit test results are getting wrongly attached to all the test cases
> ---------------------------------------------------------------------
>
>                 Key: JENKINS-12810
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12810
>             Project: Jenkins
>          Issue Type: Bug
>          Components: testlink
>    Affects Versions: current
>            Reporter: Vignesh Senapathy
>            Assignee: Bruno P. Kinoshita
>             Fix For: current
>
>         Attachments: last_tc.png, tc1.png, tc2.png
>
>
> Hi,
> I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the 
> Junit Test results are getting generated. This in turn calls the Testlink xml 
> rpc and attaches the results to the test case, but the test results are 
> attached wrongly. The 1st test case has 6 results, the next has 5 and so on 
> and the last one has 1 test result attached to it. I dont know if it is bug 
> which is causing this. Please let me know what seems to be the problems. Also 
> the execution flags are correctly rendered in this. which ever test case 
> fails is marked as failed and which passed is marked as passed.
> Also I have one custom field which maps to the test suite name and test 
> classname.

--
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