In the Clover HTML output, Clover marks JUnit tests that use the new JUnit @Rule ExpectedException to check for exceptions as failures, even though the test actually passes. I found this on the documentation: http://confluence.atlassian.com/display/CLOVER/Unit+Test+Results+and+Per-Test+Coverage however, the comment on it is not clear to me:
Clover does its best to record your test results in the Clover database. In some instances however, Clover can not always do so. Although unit tests using
@Test(expected=Exception.class)annotations will be marked as passed, more novel JUnit constructs such as rules may not be recognized and Clover will flag those tests as failed when in fact they passed. To integrate these test results into your Clover reports follow these steps:
Does this mean that this is a known issue that can/will never be fixed, or will there eventually be some fix?
I'm suffering from the same problem. ExpectedException rule is ignored and tests marked as failed even though they pass. I don't want to change 350 unit test . I'm trying to find a workaround but no success so far. I'm using Maven, please help!
Note: I'd be satisfied with just being able to say "includeFailedTestCoverage" in maven plugin.
Can't say if there are any solutions, but I'd like to note that migrating your tests from `ExpectedException` rule to `expected` parameter of `Test` annotation is not a good one: http://errorprone.info/bugpattern/TestExceptionChecker
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot