[
https://issues.apache.org/jira/browse/MRUNIT-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13424926#comment-13424926
]
Jarek Jarcec Cecho commented on MRUNIT-126:
-------------------------------------------
Having TestResult class make complete sense to me and it might be even
beneficial for the future additions (if there will be any of course).
My only concerns is backward compatibility. I see the point of breaking the API
(as user is actually missing the counters entirely), but even thought, I'm not
sure that it's completely good idea :-/ Are we still planning to do big changes
in near future (that will break a lot of the API?)
Jarcec
> 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
