[
https://issues.apache.org/jira/browse/KYLIN-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hongbin ma resolved KYLIN-697.
------------------------------
Resolution: Fixed
> Reorganize all test cases to unit test and integration tests
> ------------------------------------------------------------
>
> Key: KYLIN-697
> URL: https://issues.apache.org/jira/browse/KYLIN-697
> Project: Kylin
> Issue Type: Improvement
> Components: Tools, Build and Test
> Affects Versions: v0.6.5, v0.8.1, v0.7.1
> Reporter: hongbin ma
> Assignee: hongbin ma
>
> All of the test case in current version are treated like unit test
> cases(meaning we have no integration tests), this is leading to many problems
> including:
> 1. At Jenkins, we have to separate the test process to buildcube, buildii,
> test,,, this is troublesome, and being the wrong way.
> 2. HbaseMeatadataTestscase will pollute the classpath of subsequent
> localmetadatatestcase, as described in
> https://issues.apache.org/jira/browse/KYLIN-694.
> 3. The vague boundary between unit test and integration tests makes it
> difficult for running unit test/integration test only.
> Maven has provided a full stack of tool for cases like us. We could put all
> the unit tests in "test" phrase and all the integration tests in
> "integration-test" phrase. We can also put all the BuildCube/BuildII test
> cases to the "pre-integration-test" phrase, since they can be treated as part
> of environment preparation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
