hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4605) should run old version of unit tests to check back-compatibility
Date Wed, 12 Nov 2008 11:39:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646874#action_12646874
] 

Steve Loughran commented on HADOOP-4605:
----------------------------------------

OK, so it's only API stability at the source code level. That's much easier. What you do need
to look out for there is refactoring a class and accidentally having the changes propagate
into the API tests. That can be prevented through rigorous review or not having those tests
in your IDE when you reach for the refactoring button. 

Some ideas
* Identify those tests that are part of the API and move them into the 'stable api' corner
of the package tree
* Have a base class that they can all extend {{BackwardsCompatibleTestCase}} or similar to
identify these should be stable. 
* Have a policy about it being good to add new tests here, but changing existing tests needs
to be looked at carefully

Deprecated code could be handled specially: the tests remain but are somehow tagged to a specific
version, so it's OK to delete them when their time is up

> should run old version of unit tests to check back-compatibility
> ----------------------------------------------------------------
>
>                 Key: HADOOP-4605
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4605
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: test
>            Reporter: Doug Cutting
>
> We should test back-compatibility by running unit tests from a prior release.

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


Mime
View raw message