[
https://issues.apache.org/jira/browse/MRUNIT-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425735#comment-13425735
]
Dave Beech commented on MRUNIT-126:
-----------------------------------
What if you want to just do some manual assertions on your outputs but don't
want the hassle of duplicating counter verification code?
After all, the counter assertions are quite simple - I can't think of many
cases where the default counter verification wouldn't be good enough. But I do
use the run() method fairly frequently when I have custom writables but don't
want to do full object equality checks for my tests to pass/fail.
> 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
