mrunit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Donofrio (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MRUNIT-54) Driver.runTest throws RuntimeException should it throw AssertionError?
Date Sun, 26 Feb 2012 21:40:53 GMT

    [ https://issues.apache.org/jira/browse/MRUNIT-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216862#comment-13216862
] 

Jim Donofrio commented on MRUNIT-54:
------------------------------------

Yes I agree we should change all test assert failures to throw AssertionError instead of mixing
IOException and assert failures as RuntimeExceptions
We just have to change throw new RuntimeException(buffer.toString()); to fail(buffer.toString());
in TestDriver and update the test to catch AssertionError
                
> Driver.runTest throws RuntimeException should it throw AssertionError?
> ----------------------------------------------------------------------
>
>                 Key: MRUNIT-54
>                 URL: https://issues.apache.org/jira/browse/MRUNIT-54
>             Project: MRUnit
>          Issue Type: Bug
>            Reporter: Brock Noland
>
> The difference is small but in maven tests show up as erred not failed.

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

        

Mime
View raw message