[
https://issues.apache.org/jira/browse/KYLIN-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125809#comment-15125809
]
hongbin ma commented on KYLIN-1356:
-----------------------------------
Hi community,
>From Kylin 2.0 you can run UT, IT and environment provision for IT separately.
Running "mvn verify -Dhdp.version=2.2.4.2-2" (assume you're on your sandbox)
is all you need to run a complete all the test cases
It will execute the following steps sequentially:
1. Build Artifacts
2. Run all UTs (takes few minutes)
3. Provision the sandbox environment for IT (takes 1~3 hours)
4. Run all ITs (takes few tens of minutes)
5. verify jar stuff
If your code change is minor and it merely requires running UT, use:
mvn test
If your sandbox is already provisioned and your code change will not affect the
result of sandbox provision, (and you don't want to wait hours of provision)
just run the following commands to separately run UT and IT:
mvn test
mvn failsafe:integration-test
More About Provision Step:
Environment provision is indeed running kylin cubing jobs to prepare example
cubes in the sandbox. These prepared cubes will be used by the ITs. Currently
provision step is bound with the maven pre-integration-test phase, and it
contains running BuildCubeWithEngine (HBase required),
BuildCubeWithStream(Kafka required) and BuildIIWithStream(Kafka Required). You
can run the mvn commands on you sandbox or your develop computer. For the
latter case you need to set kylin.job.run.as.remote.cmd=true in
$KYLIN_HOME/examples/test_case_data/sandbox/kylin.properties. Try appending
-DfastBuildMode=true to mvn verify command to speed up provision by skipping
incremental cubing.
Will update the above information to our website when 2.0 is released
> use exec-maven-plugin for IT environment provision
> --------------------------------------------------
>
> Key: KYLIN-1356
> URL: https://issues.apache.org/jira/browse/KYLIN-1356
> Project: Kylin
> Issue Type: Bug
> Reporter: hongbin ma
> Assignee: hongbin ma
> Fix For: 2.0, 2.1
>
>
> currently we rely on test cases like BuildCubeWithEngineTest for IT
> environment provision. This is not the right way, trying to leverage
> exec-maven-plugin for this
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
