[
https://issues.apache.org/jira/browse/MRUNIT-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257471#comment-13257471
]
Jim Donofrio commented on MRUNIT-101:
-------------------------------------
I will add a method withOutputFormat(Class<? extends FileOutputFormat>
outputFormat, Class<? extends FileInputFormat> inputFormat). I think we should
move to users passing in classes to be more consistent with the conf instead of
instances of outputformats, mappers, etc. We can only really test classes that
extend FileOutputFormat because there is no contract on how to add input/output
to the other types. I will create a random dir mrunit-random number in
java.io.tmpdir. I will add this path to the FileOutputFormat. I will use the
FileOutputFormat to get a record writer and write out the output using a
MockOutputCollector. Then using the provided FileInputFormat I will add the
output file and call getSplits and then getRecordReader which will allow me to
read the output back in and compare the results to the expected output using
the traditional validate method
> Offer the option to use real OutputFormats instead of the MockOutputFormat
> --------------------------------------------------------------------------
>
> Key: MRUNIT-101
> URL: https://issues.apache.org/jira/browse/MRUNIT-101
> Project: MRUnit
> Issue Type: New Feature
> Affects Versions: 0.9.0
> Reporter: Jim Donofrio
> Labels: output_format
>
> Currently we only use the MockOutputFormats which just copy the output key,
> value into a list. This prevents users from testing the outputformat for
> classes such as TextOutputFormat which should compare the toString versions
> of objects for equality not the objects themselves.
--
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
