hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1050) Introduce a mock object testing framework
Date Mon, 12 Oct 2009 16:53:32 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764744#action_12764744

Konstantin Boudnik commented on MAPREDUCE-1050:

I believe {{...WithMocks}} suffix is optional, isn't it? I suggest we just drop it. I believe
we have briefly discuss it during Thursday meeting that we'll create separate folders for
different types of tests, i.e. {{src/test/unit}}, {{src/test/functional}}, {{src/test/stress}}
and so on. Then inside of these folder we don't need to have any special tags in the class
names just whatever is required by JUnit, Mockito and so on.

> Introduce a mock object testing framework
> -----------------------------------------
>                 Key: MAPREDUCE-1050
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1050
>             Project: Hadoop Map/Reduce
>          Issue Type: Test
>          Components: test
>            Reporter: Tom White
>            Assignee: Tom White
>         Attachments: MAPREDUCE-1050.patch, MAPREDUCE-1050.patch
> Using mock objects in unit tests can improve code quality (see e.g. http://www.mockobjects.com/).
Hadoop would benefit from having a mock object framework for developers to write unit tests
with. Doing so will allow a wider range of failure conditions to be tested and the tests will
run faster.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message