[
https://jira.codehaus.org/browse/SUREFIRE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=308590#comment-308590
]
Baptiste MATHUS commented on SUREFIRE-841:
------------------------------------------
I agree about being cautious about creating confusion. But still, surefire
didn't create that confusion, from what I see JUnit did by changing its
behaviour, isn't it?
I think only a small warning in the doc would prevent many users from being
surprised. And if some get surprised, well that's a JUnit-side "issue" in the
first place...
> Incorrect Test Run Count
> ------------------------
>
> Key: SUREFIRE-841
> URL: https://jira.codehaus.org/browse/SUREFIRE-841
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Reporter: karthik kandasamy
> Fix For: 2.13
>
>
> When a simple Junit test with errors in the @Before() and @After() method are
> run directly with java or ant's junit task, it reports correctly that the
> Tests Run = 1 and Errors = 2.
> But when the same is run through maven surefire plugin, it reports it as
> Tests Run = 2 and Errors = 2.
> Its the same test in which 2 errors are encountered, so the Tests Run should
> be 1.
> I traced the issue to the org.apache.maven.surefire.report.TestSetRunListener
> Class - testError() method, where the completed count is also incremented
> along with the error count irrespective of whether its in the same test the
> error is encountered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
