EricGao888 opened a new issue, #10573: URL: https://github.com/apache/dolphinscheduler/issues/10573
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description Unit Tests of high quality could not only improve the stability of Dolphin Scheduler, but also increase the readability of Dolphin Scheduler Code. * Currently we only have around 40% UT coverage. Although DS already has E2E tests and the community are working on the API tests, it never means we do not need high quality unit tests. * As a DS developer, every time after submitting PR, we will see the current UT coverage of the whole project. If the coverage is too low, developers may have concert about the stability of the application. * Reading unit tests is one of best approaches for new developers to understand the code. UT cases also help reviewers to review PR. As it is hardly possible to provide docs of every detailed feature of DS, the best way is to keep UT updated. ### Use case * We could have different standards for UT for different parts of DS. For example, we have higher bar on UT for core features but lower bar for plugins. * We could offer a list of UT cases which need to be updated, added or refactored and label them with `good first issue`. For new developers to this community, writing UT is a good way to understand the code logic and it is more intriguing than refactoring docs. ### Related issues * related: #3700 ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
