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 (Updated) (JIRA)" <ji...@apache.org> on 2012/04/18 03:57:13 UTC

[jira] [Updated] (MRUNIT-101) Offer the option to use real OutputFormats instead of the MockOutputFormat

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

Jim Donofrio updated MRUNIT-101:
--------------------------------

    Description: 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.  (was: 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 will require a good bit of worth as we need to write some kind of MemoryFileSystem class extending FileSystem since all of the OutputFormats want to write to Paths)
    
> 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