[
https://issues.apache.org/jira/browse/HADOOP-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647255#action_12647255
]
Steve Loughran commented on HADOOP-4605:
----------------------------------------
>> What you do need to look out for there is refactoring a class and
>> accidentally having the changes propagate into the API tests.
>No, I'm proposing that we can aggressively update tests as we update APIs,
>since we we'll use the older, unchanged versions of the tests (from a
>subversion tag) to check back-compatibility. We'd run two versions of the
>tests: the current and the oldest that we claim compatibility with.
In that situation the tests need to be Jarred up or something and run under
JUnit with the rest of the classpath being SVN_HEAD hadoop JARs. If the
compatibility tests are released/retained as an artifact then you can keep it
around and run junit over it with everything else from the new system. The test
suite becomes another artifact to preserve. Annotations are still good to
identify which tests to run, etc
> 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.
