[
https://issues.apache.org/jira/browse/HADOOP-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646521#action_12646521
]
Steve Loughran commented on HADOOP-4605:
----------------------------------------
>> I would prefer to have a separate set of tests, the compatibility tests,
>> that [ ... ]
>Yes, I agree. And some of our current tests fit this description and some do
>not. So, to start out down this path, we >can split out those existing tests
>that are suitable (i.e., only use public APIs). Right?
Yes, though as those test cases also bring up/tear down the cluster in-VM, you
aren't going to be able to run them against a different hadoop release than in
the classpath.
The compatibility tests will need to take the URL of a job tracker that is
already deployed, run their tests and push out the results, no start/stop of
the cluster per test-case. This will be faster anyway, it just complicates the
test setup process
> 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.
