Currently, the JavaCheckVerifier is erroring tests (throwing IllegalStateException) when some conditions are not met:
- No issues are raised during analysis, while some issues were expected
- Rules having a "Constant" remediation cost are providing a "cost to fix" (which is not supposed to happen)
- Multiple issues are reported on a file while we always expect to have a single one at file level
In order to differentiate faults in implementation (NullPointerException or IndexOutOfBoundException, for instance) from errors in the logic of the rule, the JavaCheckVerifier should fail the test, rather than erroring and throwing the exception.