[
https://issues.apache.org/jira/browse/SCB-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551480#comment-16551480
]
wujimin commented on SCB-719:
-----------------------------
should support manage test case like the below:
{code:java}
// deploy edge/zuul
// ITUtils.ensureReady(edge); // if not ready, will start a new instance and
wait for ready
// ITUtils.ensureReady(zuul);
// 1.base test case
// include all extension point abnormal scenes test case
// deploy standalone base-producer
// only run one case for "any" transport
// run highway
// run vertx-rest
// run native restTemplate to edge/zuul
// stop standalone base-producer
// deploy tomcat base-producer
// run vertx-servlet
// run native restTemplate to edge/zuul
// stop tomcat base-producer
// deploy sprint boot base-producer
// run vertx-servlet
// run native restTemplate to edge/zuul
// stop spring boot base-producer
// 2.complex test case
// 1)start new producer version
// consumer/edge/zuul should ......
// 2)delete new producer version
// consumer/edge/zuul should ......
// ......
// 3.deploy development mode producer
// ......
{code}
> 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
>
> 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)
