Add shardingsphere-scenario

[tuohai666]

Please fill up those following information before send Pull request

• Pull request NO: #1934 (Provide plugin for ShardingSphere apache/skywalking#1934)
• Agent repository URL: https://github.com/tuohai666/incubator-skywalking
• Testcases repository URL: https://github.com/tuohai666/skywalking-agent-testcases

[ascrutae]

There are three faults in this test case:

1. The test case container miss the MySQL environment variable
2. The MySQL environment variables is not read by test case. It use the default value and those value cannot run in container environment, it will happen exception that the network cannot reach.
3. There are lots of fields value is incorrect. For example: spanId , parentSpanID

[ascrutae]

Suggested change

	image: skywalking/skywalking-mock-collector:{COLLECTOR_IMAGE_VERSION}
	image: skyapm/mock-collector:{COLLECTOR_IMAGE_VERSION}

[ascrutae]

Suggested change

	value: http://localhost:18080/shardingsphere-case/case/execute
	value: http://localhost:{SERVER_OUTPUT_PORT}/shardingsphere-case/case/execute

[tuohai666]

fixed

[ascrutae]

I suggest that you should make sense the value of parentTraceSegmentId

[tuohai666]

The parent trace segmentId is unpredictable. During the last test is segmentId is .1.15562751912310010. Any suggestion?

[ascrutae]

I suggest that you should make sense the value of parentTraceSegmentId

[ascrutae]

@tuohai666 I can't see any information about data sharding or database orchestration from expected data. Is that miss this information in this scenario?

[tuohai666]

@ascrutae Thanks for your comments. The test case is a single routing scenario, and the expected data is same as actual data.

@tuohai666 I can't see any information about data sharding or database orchestration from expected data. Is that miss this information in this scenario?

[wu-sheng]

Thanks for your comments. The test case is a single routing scenario, and the expected data is same as actual data.

@tuohai666 Is single DB routing scenario enough? This case is designed to verify the plugin and benefit for shardingsphere ecosystem. We can't make that decision, but I think as a routing lib, it should test at least for two DBs.
@terrymanu @tristaZero What do you think? Or prefer?

[tuohai666]

@wu-sheng Thanks for quick reply. I have tried full routing before this version of test case. The problem is that full routing can not guarantee the order of the executing threads, and leads to an unpredictable spans order.

[terrymanu]

If SkyWalking's test framework can assert for concurrency(ignore execute's spans order), I prefer use two DBs scenario.
If not, use single DB is fine too. From technical layer, single DB and two DBs are really similar (beside a new thread and merge engine, but merge is not monitored by SkyWalking)

[ascrutae]

Suggested change

	parentTraceSegmentId: not null
	parentTraceSegmentId: "${Your_ApplicationName[3]}"

[ascrutae]

Suggested change

	parentTraceSegmentId: not null
	parentTraceSegmentId: "${Your_ApplicationName[3]}"

[ascrutae]

Suggested change

	parentTraceSegmentId: not null
	parentTraceSegmentId: "${Your_ApplicationName[3]}"