[
https://issues.apache.org/jira/browse/HBASE-7938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601945#comment-13601945
]
Nick Dimiduk commented on HBASE-7938:
-------------------------------------
bq. No need to do fancy stuff. We can just call the tests one-by-one within
run().
Are you sure? That sounds brittle? IntegrationTestsDriver invokes JUnit
manually; I'd prefer to leave this up to the driver.
bq. This looks like the IntegrationTestingUtility didn't clean up the test
directory after a run.
I assumed way too much. HBaseCluster#restoreClusterStatus() does nothing, thus
IntegrationTestingUtility#restoreCluster() does nothing. Does this mean paths
returned by HBaseTestingUtility#getDataTestDirOnTestFS() are not cleaned after
a test? Sad panda.
> Add integration test for ImportTsv/LoadIncrementalHFiles workflow
> -----------------------------------------------------------------
>
> Key: HBASE-7938
> URL: https://issues.apache.org/jira/browse/HBASE-7938
> Project: HBase
> Issue Type: Sub-task
> Components: mapreduce
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.95.0, 0.98.0
>
> Attachments:
> 0001-HBASE-7938-Add-integration-test-for-ImportTsv-LoadIn.patch
>
>
> 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
