kezhenxu94 commented on a change in pull request #8037:
URL: https://github.com/apache/skywalking/pull/8037#discussion_r738937756



##########
File path: docs/en/guides/README.md
##########
@@ -50,16 +50,15 @@ Since version 6.3.0, we have introduced more automatic 
tests to perform software
 > End-to-end testing is a methodology used to test whether the flow of an 
 > application is performing as designed from start to finish.
  The purpose of carrying out end-to-end tests is to identify system 
dependencies and to ensure that the right information is passed between various 
system components and systems.
 
-The E2E test involves some/all of the OAP server, storage, coordinator, 
webapp, and the instrumented services, all of which are orchestrated by 
`docker-compose`. Besides, there is a test controller (JUnit test) running 
outside of the container that sends traffic to the instrumented service,
-and then verifies the corresponding results after those requests have been 
made through GraphQL API of the SkyWalking Web App.
+The E2E test involves some/all of the OAP server, storage, coordinator, 
webapp, and the instrumented services, all of which are orchestrated by 
`docker-compose`. 
+Since version 8.9.0, we immigrate to e2e-v2 which leverage 
[skywalking-infra-e2e](https://github.com/apache/skywalking-infra-e2e) and 
[skywalking-cli](https://github.com/apache/skywalking-cli) to do the whole e2e 
process.
+`skywalking-infra-e2e` is using to control the e2e process and 
`skywalking-cli` is using to interact with the OAP such as request and get 
response metris from OAP.

Review comment:
       ```suggestion
   `skywalking-infra-e2e` is used to control the e2e process and 
`skywalking-cli` is used to interact with the OAP such as request and get 
response metris from OAP.
   ```
   




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to