|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
Can we please have this one reopened? First of all, it's not true that JUnit 4 does not distinguish between failure and errors any more. See the how-to at [1] (which is linked form the official JUnit site at [2]) for details. Secondly, reporting errors as failures masks the real problem, and thus is bad practice. For example, a native crash in a third-party library that is called via JNI results in the test suite / VM to crash. This is reported as an error by JUnit, but as a failure by Jenkins, which makes it really hard to discover at the first glance.
[1] http://pub.admc.com/howtos/junit4x/methods-chapt.html#N10201
[2] http://www.junit.org/node/507