[
https://issues.apache.org/jira/browse/PHOENIX-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900967#comment-13900967
]
Enis Soztutar commented on PHOENIX-42:
--------------------------------------
This looks good. Some of the code is "borrowed" from IntegrationTestsDriver in
HBase, which shares the same goal.
bq. One question: what's the difference between calling
util.startMiniCluster()/util.shutdownMiniCluster() versus
util.initializeCluster(1)/util.restoreCluster()? Will this make our unit tests
run faster?
initializeCluster() calls startMiniCluster() in case of a mini hbase cluster.
In case of a distributed cluster, it initializes some cluster state. The test
calls initCluster() because it does not know whether it is a mini or an actual
cluster.
> Provide end2end test command line utility
> -----------------------------------------
>
> Key: PHOENIX-42
> URL: https://issues.apache.org/jira/browse/PHOENIX-42
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Jeffrey Zhong
> Assignee: Jeffrey Zhong
> Fix For: 3.0.0
>
> Attachments: PHOENIX-42.patch
>
>
> Currently end2end tests run against a HBaseMiniCluster not a real cluster.
> This JIRA is to provide a utility to run end2end tests against a real testing
> cluster.(Don't run it against production cluster because it will clean all
> data in the testing cluster)
> The utility will be placed under bin folder and a user needs to set hbase
> config path, phoenix jar path and hbase library path correctly before
> invoking the utility.
> {code}
> Usage:
> 1) Print all end2end tests included without really running them
> /usr/lib/phoenix/bin/end2endTest.sh -n
> 2) Run a single end2end test suite
> /usr/lib/phoenix/bin/end2endTest.sh -r <TestSuiteName>
> For example, /usr/lib/phoenix/bin/end2endTest.sh -r IndexMetadataTest
> 3) Run all end2end tests
> /usr/lib/phoenix/bin/end2endTest.sh
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
