[
https://issues.apache.org/jira/browse/HADOOP-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646548#action_12646548
]
Steve Loughran commented on HADOOP-4605:
----------------------------------------
>> you aren't going to be able to run them against a different hadoop release
>> than in the classpath.
>picking the right binaries by overriding some ant parameter shouldn't be much
>hard, no?
the problem is you want to run junit with one version of JARs and the server
should be a different set. An Ant property can drive this, but you do need to
start up Hadoop outside of Junit, run the tests then tear the cluster down
>> This will be faster anyway, it just complicates the test setup process
>Yes, it will complicate a lot and automating the runs won't be trivial then.
No, not at all. It is still easy to test, just not within a single JUnit
TestCase.
1. some slides on how we do functional testing, including interop testing
across the internet with other implementations of the same WS-* spec:
http://wiki.smartfrog.org/wiki/display/sf/Presentations
2. To actually do functional testing of smartfrog (other than running tests
under it) we have a special functional test task that starts our server in one
process, blocks until the server is live, runs the tests, then does cleanup in
the <finally> stage. I've proposed providing a rewrite to Ant1.8:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44242
however, you can grab our existing task and use it in Ant today, which would
let hadoop have a set of test cases that could be run against a live server
that had been brought up with a different classpath.
> 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.
