You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrunit.apache.org by "Brock Noland (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/17 15:41:38 UTC

[jira] [Resolved] (MRUNIT-68) Support custom counter checking

     [ https://issues.apache.org/jira/browse/MRUNIT-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brock Noland resolved MRUNIT-68.
--------------------------------

    Resolution: Fixed
      Assignee: Jarek Jarcec Cecho

OK, neither of those look like review items big enough to hold up a commit.  Jim, if you feel differently we can continue to discuss this post commit since we have a CTR (commit then review) policy on this project.

Committed in 1301944.

Thank you for your contribution Jarek!
                
> Support custom counter checking
> -------------------------------
>
>                 Key: MRUNIT-68
>                 URL: https://issues.apache.org/jira/browse/MRUNIT-68
>             Project: MRUnit
>          Issue Type: New Feature
>    Affects Versions: 0.8.1
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.0.0
>
>         Attachments: MRUNIT-68.patch, MRUNIT-68.patch, MRUNIT-68.patch, MRUNIT-68.patch
>
>
> It would be great if user could check custom counter values in addition to checking outputs. Let me show my idea on example, right now counters needs to be checked explicitly:
> assertEquals(2, mapDriver.getCounters().findCounter(CustomMapper.CustomCounter.NAME).getValue());
> It would be great if user could do something like:
> .withCounter(CustomMapper.CustomCounter.Name, 2)

--
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