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-1637) Create a test for API compatibility between releases
Date Fri, 26 Mar 2010 18:00:28 GMT

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

Konstantin Boudnik commented on MAPREDUCE-1637:

Tom, I believe this is much bigger issue and needs to be addressed for all Hadoop components.
But MR is a good start as any :)

My strong impression that the best approach without going over (i.e. creating a TCK of some
sort) is to have good unit test coverage. I'm not talking about JUnit based functional tests
Hadoop posses in overwhelming quantities, but rather about actual unit tests which verify
that methods (units) returns expected types/results when a pre-defined set of parameters is
passed in. 

Then whenever an API is being changed it will immediately trigger compilation failure in said
unit tests. If a unit test needs to be changed to fix the compilation error then it has to
be marked (with some sort of annotation?) as a compatibility issue. Such tags are easy to
gather automatically later on.

> Create a test for API compatibility between releases
> ----------------------------------------------------
>                 Key: MAPREDUCE-1637
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1637
>             Project: Hadoop Map/Reduce
>          Issue Type: Test
>          Components: build, test
>            Reporter: Tom White
>             Fix For: 0.21.0
> We should have an automated test (or a set of tests) for checking that programs written
against an old version of the API still run with a newer version. 

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

View raw message