peng-yongsheng opened a new issue #1034: Collector automated testing for 
storage module
   Please answer these questions before submitting your issue.
   - Why do you submit this issue?
   - [X] Feature or performance improvement
   ### Requirement or improvement
   - Please describe about your requirements or improvement suggestions.
   In the feature, there will be several storage implementations, such as H2, 
ElasticSearch transport client, ElasticSearch Rest client, ShardingJDBC. But to 
this day, we determine whether a system functions as intended by the manual 
test. It's too hard to ensure all of them have the same implementations.
   Discuss how to do it. @wu-sheng @acurtain @wengangJi
   ## Overview of automated testing projects
   - Forked source codes
   - Test toolkit
   - Docker compose
   ### Forked source code
   The source codes where the project resides, contributors fork the 
"incubator-skywalking" project and program the storage module implementation 
with different database.
   [Source code project]({Account ID}/{forked project name 
from incubator-skywalking})
   ### Test toolkit
   The source codes which used to mock datas, send to the collector, verify the 
datas, shell script for startup.
   Shell script: 
   1. Variable definition: Forked project git address, Docker compose project 
git address
   1. Maven package the forked project
   1. Maven package toolkit project
   1. Get the docker compose define and run
   ### Docker compose( Create new project when it not exist )
   This project contains the docker compose define, collector application 
config file. 
   Docker compose: 
   - Define database service uses a public image
   - Bind mount for forked project package and toolkit project package
   Config file: 
   - Config the database information because of this file could not PR into 
"incubator-skywalking" project. The "incubator-skywalking" project default 
storage must use H2 implementation.
   [Docker compose]([database 
   Database name for example: h2, es-transport, es-rest

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to