You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrunit.apache.org by "Jim Donofrio (Created) (JIRA)" <ji...@apache.org> on 2012/03/08 04:05:12 UTC

[jira] [Created] (MRUNIT-74) Matching output but at incorrect position is not returned as an Error in the message string thrown in the RuntimeException

Matching output but at incorrect position is not returned as an Error in the message string thrown in the RuntimeException
--------------------------------------------------------------------------------------------------------------------------

                 Key: MRUNIT-74
                 URL: https://issues.apache.org/jira/browse/MRUNIT-74
             Project: MRUnit
          Issue Type: Improvement
    Affects Versions: 0.8.1
            Reporter: Jim Donofrio
            Priority: Minor


It seems strange to me to not return "0 Error(s): ()" in the now RuntimeException but soon to be AssertionError when the output is correctly matched but in the incorrect order

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

        

[jira] [Updated] (MRUNIT-74) Matching output but at incorrect position is not returned as an Error in the message string thrown in the RuntimeException

Posted by "Jim Donofrio (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MRUNIT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Donofrio updated MRUNIT-74:
-------------------------------

    Fix Version/s: 1.0.0
    
> Matching output but at incorrect position is not returned as an Error in the message string thrown in the RuntimeException
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRUNIT-74
>                 URL: https://issues.apache.org/jira/browse/MRUNIT-74
>             Project: MRUnit
>          Issue Type: Improvement
>    Affects Versions: 0.8.1
>            Reporter: Jim Donofrio
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> It seems strange to me to not return "0 Error(s): ()" in the now RuntimeException but soon to be AssertionError when the output is correctly matched but in the incorrect order

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

        

[jira] [Resolved] (MRUNIT-74) Matching output but at incorrect position is not returned as an Error in the message string thrown in the RuntimeException

Posted by "Jim Donofrio (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MRUNIT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Donofrio resolved MRUNIT-74.
--------------------------------

    Resolution: Fixed

Edited lookupExpectedValue to also take a List<String> errors in order to add the logged errors relating to "Received unexpected output" and "Matched expected output but at incorrect position" to the exception message

Also corresponding with MRUNIT-48 throw more meaningful error for Received unexpected output when key, value actual class doesnt match any of the expected classes under the assumption that only one concrete class (no subclasses) is used for the key and one class for the value.

Updated tests to pass based on the exception message changing

committed in 1299567
                
> Matching output but at incorrect position is not returned as an Error in the message string thrown in the RuntimeException
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRUNIT-74
>                 URL: https://issues.apache.org/jira/browse/MRUNIT-74
>             Project: MRUnit
>          Issue Type: Improvement
>    Affects Versions: 0.8.1
>            Reporter: Jim Donofrio
>            Assignee: Jim Donofrio
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> It seems strange to me to not return "0 Error(s): ()" in the now RuntimeException but soon to be AssertionError when the output is correctly matched but in the incorrect order

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

        

[jira] [Assigned] (MRUNIT-74) Matching output but at incorrect position is not returned as an Error in the message string thrown in the RuntimeException

Posted by "Jim Donofrio (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MRUNIT-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Donofrio reassigned MRUNIT-74:
----------------------------------

    Assignee: Jim Donofrio
    
> Matching output but at incorrect position is not returned as an Error in the message string thrown in the RuntimeException
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRUNIT-74
>                 URL: https://issues.apache.org/jira/browse/MRUNIT-74
>             Project: MRUnit
>          Issue Type: Improvement
>    Affects Versions: 0.8.1
>            Reporter: Jim Donofrio
>            Assignee: Jim Donofrio
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> It seems strange to me to not return "0 Error(s): ()" in the now RuntimeException but soon to be AssertionError when the output is correctly matched but in the incorrect order

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