[ https://issues.jenkins-ci.org/browse/JENKINS-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruno P. Kinoshita updated JENKINS-11894: ----------------------------------------- Attachment: testlink.hpi TestLink 3.1-alpha What still needs to be tested: - Distributed environment (slave, master) - Win + Linux - Different results seeking strategies - Wrong HTML help files or messages not being translated For this issue, testing if the test methods are being found correctly is enough. But should you find any problem with distributed env., messages, etc, please feel free to drop a message or create an issue Thank you in advance! > All tests {test Methods} of TestNG, belonging to the same class are shown as > "FAILURE", if just one of the test is a failure > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JENKINS-11894 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11894 > Project: Jenkins > Issue Type: Bug > Components: testlink > Environment: Jenkins Version 1.440 {Testlink Plugin - Version 3.0.2} > Testlink Version 1.9.3 (Prague) > Reporter: Venugopal Shenoy > Assignee: Bruno P. Kinoshita > Priority: Critical > Labels: plugin > Attachments: testlink.hpi, testng-results.xml > > > Create one TestNG test class with several test methods {say 3 methods}. One > of the test is deliberately failed {using assertTrue(false);}. All the > tests are shown as failure in Testlink, when the testng xml test results are > pushed to testlink using the Jenkins-Testlink plugin. {TestNG XML Results > file is attached} -- 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