Hi Willem and Sheng, Thanks a lot for your help. It's great you have already created mature testing procedure. I'll refer to your advice before I start to work.
Sheng Wu <[email protected]> 于2019年11月14日周四 上午9:09写道： > SkyWalking is using multiple types[1] of tests for every commit tests, it > is a kind of acceptance test. > > 1. Integration Tests, like ServiceComb's > 2. e2e tests, after recompiling the whole tar ball, run the real case and > check input/output[2][3] > 3. Component tests. In SkyWalking, they are agent plugin tests. You need to > go through different cases and verify the output. In SS, it means, > verifying the route dest and rewritten SQLs at mock DB sides. > > The whole test process is a long term to build, please set the priority, > these above are just material to give you some ideas. > > [1] > > https://github.com/apache/skywalking/blob/master/docs/en/guides/README.md#for-code-developer > [2] https://github.com/apache/skywalking/tree/master/test/e2e > [3] > > https://builds.apache.org/blue/organizations/jenkins/skywalking-e2e-2/detail/skywalking-e2e-2/1822/pipeline/ > > Sheng Wu 吴晟 > > Apache SkyWalking > Apache Incubator > Apache ShardingSphere, ECharts, DolphinScheduler podlings > Zipkin > Twitter, wusheng1108 > > > Willem Jiang <[email protected]> 于2019年11月13日周三 下午9:48写道： > > > Please take the accept test[1] in ServiceComb Pack as an example, it's > > quite simple you just need to provide a date access API. > > Here is a Chinese blog[2] you can take a look at. > > > > [1] > > > https://github.com/apache/servicecomb-pack/tree/SCB-1587/acceptance-tests > > [2] > > > https://servicecomb.apache.org/cn/docs/how-to-do-microservice-accept-test/ > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Wed, Nov 13, 2019 at 8:28 PM Zhang Yonglun <[email protected]> > > wrote: > > > > > > Hi all, > > > > > > I'd like to setup an acceptance test environment which could cover the > > > basic scenarios for ShardingSphere. > > > > > > It focuses on function test but not performance test. We can test any > > tags > > > or branches of the GitHub repository. It's convenient to verify > > > the influence of a new feature, especially to releasing process. > > > > > > I suppose to setup the environment in https://builds.apache.org, and > > > install MySQL server in this cluster from the Docker Hub. Is it > compliant > > > to just use MySQL? > > > > > > I think the test scenarios should include: > > > > > > Access: > > > Sharding-JDBC > > > Sharding-Proxy > > > > > > Mode: > > > Single routing > > > Database routing > > > Table routing > > > Full routing > > > MasterSlave > > > MasterSlave + Single routing > > > MasterSlave + Database routing > > > MasterSlave + Table routing > > > MasterSlave + Full routing > > > Encryption > > > Encryption + Single routing > > > Encryption + Database routing > > > Encryption + Table routing > > > Encryption + Full routing > > > > > > SQL: > > > INSERT > > > UPDATE > > > SELECT > > > DELETE > > > Access(2) * Mode(14) * SQL(4) = 112 secnarios > > > > > > > > > -- > > > Zhang Yonglun > > > Apache ShardingSphere > > > -- Zhang Yonglun Apache ShardingSphere
