Integration test cases Improvement Project

[AlbumenJ]

Background

Integration testing is mainly based on Dubbo Samples repo use cases for completion.

Each time GitHub Actions is run, the integration test code will be automatically pulled, and the IT test cases under the test package will be run independently.

The Dubbo Samples warehouse use cases are tested using Junit4 to be compatible with Spring 4 + Springboot 1.x testing.

How to know what needs to be completed

• By comparing with the examples listed on the official website https://dubbo.apache.org/en/docs/v2.7/user/examples/, add missing use cases
• You can learn about the functions provided by Dubbo in the process of supplementing the main warehouse unit test cases (some are optional functions that can be enabled based on a switch), and add them to the verification of the integration test
• There have been useful examples and some are just for simple verification, you can try to improve coverage
• Add the boundary conditions that you think you may encounter or encountered in production into the integration test. Please submit them under dubbo-samples-boundary-test module.
• A Readme.md file is required for each sub-project except for the test-only use exception, which briefly describes the role of the use case and how to use it.

How To

• Submit your PR which contains the test cases directly to apache/dubbo.
• Leave a comment under this Issue so that we can track this project. You can just simply comment like @AlbumenJ have submit a PR #xxxx(replaced with the PR number) about NacosRegistry(replaced with the related feature) to improve test coverage.

For Newcomer

• You can learn about Dubbo's basic description and instructions on the official website of Apache Dubbo (https://dubbo.apache.org/en/)
• Fork Dubbo repo https://github.com/apache/dubbo, Dubbo Samples repo https://github.com/apache/dubbo-samples brakes on subsequent submissions and contributions to the repo
• Read the contributor's guide (can solve most of the problems that may be encountered during the participation process)
  • https://github.com/apache/dubbo#contributing
  • https://dubbo.apache.org/zh/docs/contribution-guidelines/
  • https://github.com/apache/dubbo/blob/master/CONTRIBUTING.md
  • Guide: Contributing to Dubbo dubbo#7231
• Read the Samples Test test tool documentation (involving integration testing)
  • https://github.com/apache/dubbo-samples/tree/master/test#readme
  • https://github.com/apache/dubbo-samples/blob/master/test/quick-start_cn.md
• Pull Dubbo repo and Dubbo Samples repo to the local, try to modify and improve
• If you encounter any problems during this process, you have the following contact methods
  • Ask the mail group for help: send to dev@dubbo.apache.org using personal email
  • Submit a question: Submit a question in the corresponding warehouse

Notice

• Integration testing needs to rely on the use of test tools, please read the relevant documentation first
• The new sub-module submitted needs to contain the relevant configuration files of the test framework and the standardized pom file