[
https://issues.apache.org/jira/browse/SCB-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujimin updated SCB-719:
------------------------
Description:
currently we only support simple integration test
if a test case need to start/stop microservice instance, then must run it
manually, it's not so good.
so we need to create a mechanism to support complex integration test.
1.support multiple node
because Travis CI docker container resources are limited, so must start
multiple containers
2.not depend on docker, can run in windows too.
-3.support run in IDE equals run unit test-
abandon
because it's too difficult to manage microservice instance lifecycle and
junit test class lifecycle
some microservice instances should share cross many test class, and some
microservice instances only used by one test class
junit child test suite always run duplicate when whole project or package.
4.support run by java -jar ......
was:
currently we only support simple integration test
if a test case need to start/stop microservice instance, then must run it
manually, it's not so good.
so we need to create a mechanism to support complex integration test.
1.support multiple node
because Travis CI docker container resources are limited, so must start
multiple containers
2.not depend on docker, can run in windows too.
3.support run in IDE equals run unit test
4.support run by java -jar ......
> support complex integration test
> --------------------------------
>
> Key: SCB-719
> URL: https://issues.apache.org/jira/browse/SCB-719
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Java-Chassis
> Reporter: wujimin
> Assignee: wujimin
> Priority: Major
> Attachments: image-2018-07-07-08-31-37-950.png,
> image-2018-07-07-08-35-01-791.png
>
>
> currently we only support simple integration test
> if a test case need to start/stop microservice instance, then must run it
> manually, it's not so good.
>
> so we need to create a mechanism to support complex integration test.
> 1.support multiple node
> because Travis CI docker container resources are limited, so must start
> multiple containers
> 2.not depend on docker, can run in windows too.
> -3.support run in IDE equals run unit test-
> abandon
> because it's too difficult to manage microservice instance lifecycle and
> junit test class lifecycle
> some microservice instances should share cross many test class, and some
> microservice instances only used by one test class
> junit child test suite always run duplicate when whole project or package.
> 4.support run by java -jar ......
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
