[
https://issues.apache.org/jira/browse/MRUNIT-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425744#comment-13425744
]
Dave Beech commented on MRUNIT-126:
-----------------------------------
Well, true, but if you don't care about the counters I'd expect you not to have
specified any counter conditions using withCounter etc.
How about this for a solution?
Instead of adding a new method, we could add a boolean parameter verifyCounters
to the current run method, which you will set to say whether or not you want
the automatic counter verification code to run.
The no-arg run method would delegate to run(false) to preserve current
behaviour.
> Counter tests are ignored if test is executed using run() rather than
> runTest()
> -------------------------------------------------------------------------------
>
> Key: MRUNIT-126
> URL: https://issues.apache.org/jira/browse/MRUNIT-126
> Project: MRUnit
> Issue Type: Bug
> Affects Versions: 0.9.0
> Reporter: Dave Beech
>
> An alternative way of running an mrunit test is to call run(), which returns
> the output list to you for manual validation, rather than runTest() which
> validates everything automatically.
> If you run a test using the run() method, any counter tests you have
> specified via withCounter(..) etc are silently ignored, which may falsely
> give the impression that these tests have passed.
> At the very least we should give a warning that this is happening. Otherwise,
> we should make sure the counter validation is triggered in all cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
