[
https://issues.jenkins-ci.org/browse/JENKINS-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158903#comment-158903
]
Bruno P. Kinoshita commented on JENKINS-11894:
----------------------------------------------
Just a quick update, since Thursday I have been working re-designing the
classes that the plug-in use to use Jenkins TestNG and JUnit parsers (was using
customized ones), as well as creating a new model of Result Seekers.
Now, a result seeker will be an Extension Point. And the user will be able to
select as many Result Seekers as he/she wishes. Each one has a single
responsibility, like seeking by JUnit Suite Result name, or by JUnit Case Class
name, TestNG Test Method name, and so it goes.
At same time, I'm merging two pull requests from users/developers in Github.
One of them enables the user to use a surefire-like expression to find results.
It will be a new Result Seeker too.
And I will try to add a XPath Result Seeker. This one will be able to look for
results using a XPath expression. So, in case you need to, say, look for test
methods, within only certain suite, you'll be able to do so using this Result
Seeker. However, this XPath Result Seeker needs a more thorough study. I will
read Selenium's code, to see how they look for elements, and will create a new
issue for this, with due date for March.
A last note here, I'm working on this issue, and on 11393 at same time. Trying
to add this new feature, and enhance the memory allocation at same time. So
there are some parts that would be simple to refactor, but that are demanding
more time due to memory enhancements. Allow me to delay this issue few days to
finish this refactor and test. Besides testing what was fixed in the issues, I
always test in distributed environments, with different languages, and many
other types of tests, some listed here:
https://wiki.jenkins-ci.org/display/JENKINS/Release+check+list. It reduces the
need to repeat many iterations for testing the plug-in :-)
Have a good weekend!
Cheers, -B
> 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: 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
