[
https://issues.apache.org/jira/browse/MRUNIT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497823#comment-13497823
]
Patrick Hunt commented on MRUNIT-158:
-------------------------------------
Perhaps I missed it, is there another way to easily determine why my MRUnit
test was failing? (other than say running a debugger)
I listed it as a bug/critical due to the fact that I couldn't actually figure
out why my test was failing. Isn't that reasonable to expect to be able to do
here?
I eventually subclassed MapWritable and added my own toString, that allowed me
to see why the test was failing, however it assumes the user will be able to
modify the source (which they won't in all cases if including some third party
code).
> withOutput doesn't generate useful information with MapWritable on error
> ------------------------------------------------------------------------
>
> Key: MRUNIT-158
> URL: https://issues.apache.org/jira/browse/MRUNIT-158
> Project: MRUnit
> Issue Type: Improvement
> Affects Versions: 0.9.0
> Reporter: Patrick Hunt
> Priority: Minor
>
> Using withOutput generates the following, notice that the hashcode is printed
> rather than some useful detail as to the content of the maps:
> Nov 9, 2012 2:40:01 PM org.apache.hadoop.mrunit.TestDriver logError
> SEVERE: Missing expected output (null-0, org.apache.hadoop.io.MapWritable@e1)
> at position 0.
> Nov 9, 2012 2:40:01 PM org.apache.hadoop.mrunit.TestDriver logError
> SEVERE: Received unexpected output (null-0,
> org.apache.hadoop.io.MapWritable@2059) at position 0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
