Repository: kylin Updated Branches: refs/heads/document ce2828c5a -> bedaed878
enhance how_to_test document Project: http://git-wip-us.apache.org/repos/asf/kylin/repo Commit: http://git-wip-us.apache.org/repos/asf/kylin/commit/bedaed87 Tree: http://git-wip-us.apache.org/repos/asf/kylin/tree/bedaed87 Diff: http://git-wip-us.apache.org/repos/asf/kylin/diff/bedaed87 Branch: refs/heads/document Commit: bedaed87808a39d5724cba3da68e9ea0d380f9a5 Parents: ce2828c Author: Li Yang <liy...@apache.org> Authored: Wed Sep 13 18:27:27 2017 +0800 Committer: Li Yang <liy...@apache.org> Committed: Wed Sep 13 18:27:27 2017 +0800 ---------------------------------------------------------------------- website/_dev/howto_test.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kylin/blob/bedaed87/website/_dev/howto_test.md ---------------------------------------------------------------------- diff --git a/website/_dev/howto_test.md b/website/_dev/howto_test.md index 62a4e4a..b569812 100644 --- a/website/_dev/howto_test.md +++ b/website/_dev/howto_test.md @@ -9,15 +9,16 @@ In general, there should be unit tests to cover individual classes; there must b ## Test v1.5 and above -* `mvn test` to run unit tests, which has a limited test coverage. +* `mvn clean test` runs unit tests, which has a limited test coverage. * Unit tests has no external dependency and can run on any machine. * The unit tests do not cover end-to-end scenarios like build, merge, and query. * The unit tests take a few minutes to complete. -* `dev-support/test_all_against_hdp_2_2_4_2_2.sh` to run integration tests, which has the best test coverage. +* `dev-support/test_all_against_hdp_2_4_0_0_169.sh` runs integration tests, which has the best test coverage. * Integration tests __better be run on a Hadoop sandbox__. We suggest to checkout a copy of code in your sandbox and direct run the test_all_against_hdp_2_2_4_2_2.sh in it. If you don't want to put codes on sandbox, refer to __More on v1.5 UT/IT separation__ * As the name indicates, the script is only for hdp 2.2.4.2, but you get the idea of how integration test run from it. * The integration tests start from generate random data, then build cube, merge cube, and finally query the result and compare to H2 DB. * The integration tests take one to two hours to complete. +* `nohup dev-support/test_all_against_hdp_2_4_0_0_169.sh < /dev/null 2>&1 > nohup.out` runs IT in an unattended mode. ## Test v1.3 and below
