[
https://issues.apache.org/jira/browse/MRUNIT-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423044#comment-13423044
]
Jim Donofrio commented on MRUNIT-119:
-------------------------------------
I know that withCounter does this in TestDriver but withStrictCounterChecking
in TestDriver does not need to return this because nothing uses its return
value, it should probably also be protected since no user needs to call it.
validateExpectedAgainstActual should be private, only TestDriver uses it
Good work, thanks for your contribution and sorry about out slow response, we
look forward to more of our your contributions
> Counter tests should support assertions that counters are not present
> ---------------------------------------------------------------------
>
> Key: MRUNIT-119
> URL: https://issues.apache.org/jira/browse/MRUNIT-119
> Project: MRUnit
> Issue Type: Improvement
> Affects Versions: 1.0.0
> Reporter: Dave Beech
> Priority: Minor
> Attachments: mrunit-119-proposal.diff, mrunit-119-proposal.diff
>
>
> From Bertrand Dechoux via user mailing list.
> Should we add a feature to the counter checking feature so that users can
> assert that something will *not* be present, for example an error or
> exception counter, and have the test fail if it is set?
--
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
