[
https://issues.apache.org/jira/browse/HBASE-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596387#comment-13596387
]
Enis Soztutar commented on HBASE-7938:
--------------------------------------
bq. d like to modify IntegrationTestsDriver to accept any class that implements
Tool. With that change, I can modify the existing unit tests to implement a run
method where the prickly scenarios can be run against an external cluster, as
configured by IntegrationTestsDriver
Having ITs being able to run from command line, or as an integration test or a
unit test gives us the most flexible approach. For example, recently added
TestLoadAndVerify does have this.
How do you plan to have IntegrationTestsDriver discover these tests, and figure
out the arguments?
> Add integration test for various MapReduce workflows
> ----------------------------------------------------
>
> Key: HBASE-7938
> URL: https://issues.apache.org/jira/browse/HBASE-7938
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Reporter: Nick Dimiduk
> Fix For: 0.95.0, 0.98.0, 0.94.7
>
>
> We have existing unit tests for smoke-testing the packaged MR jobs, however
> they do not create a runtime environment that is true to running on a real MR
> cluster. This is particularly true in regard to classpaths (HBASE-7934) but
> also other static state (HBASE-4802). An integration test that can be pointed
> to run on a pseudo-distributed Hadoop deployed on localhost would find these
> kinds of problems.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
