It would be nice to provide a clear context, otherwise I can only speculate.
1:It is possible that there is a problem with PowerMock, and there is no good solution for it. You can refer to [1]. Or avoid using the @Prefortest annotation. I don't know much about your specific problem, so I can't give you much help 2:Did you add the relevant test class in the root pom? [1] https://github.com/powermock/powermock/wiki/Code-coverage-with-JaCoCo Best Wishes！ CalvinKirs, Apache DolphinScheduler PMC On 07/2/2021 11:16，Yuanhao Ji<[email protected]> wrote： I’m sorry. Please see: https://github.com/apache/dolphinscheduler/runs/2465779491 Hemin Wen <[email protected]>于2021年7月2日 周五10:51写道： hello! The image in the mail cannot view, can you send detailed error information. -------------------- Apache DolphinScheduler Commtter Hemin Wen 温合民 [email protected] -------------------- Yuanhao Ji <[email protected]> 于2021年7月1日周四 下午9:50写道： Hello, everyone! I'm dealing with the problem of *incorrect unit test coverage in the API module*. First, I want to ask if anyone has encountered this problem or have any suggestions? [image: image.png] In addition, my thoughts on this problem are as follows: 1. First of all, we should find out the cause of this problem. It is preliminarily speculated that this problem is caused by the *@PrepareForTest annotation of Powermock*. 2. When the cause of the problem is accurately identified, I'll fix it. 3. In addition, I will further write a complete and detailed *document for the unit test of the API module* to remind developers what problems should be paid attention to when writing unit test codes. Look forward to your suggestions!
