shink commented on issue #5781:
URL: 
https://github.com/apache/dolphinscheduler/issues/5781#issuecomment-877661873


   @CalvinKirs Yes, I am willing to fix it.
   
   Further, how is this problem represented in the Jacoco report?
   
   > The typical symptom of class id mismatch is classes not shown as covered 
although they have been executed during the test. This situation can be easily 
detected e.g. in the HTML report: Open the Sessions page with the link on the 
top-right corner. You see a list of all classes where execution data has been 
collected for. Find the class in questions and check whether the entry has a 
link to the corresponding coverage report page. If the entry is not linked this 
means there is a class id mismatch between the class used at runtime and the 
class provided to create the report. —— [How can I detect that I have a problem 
with class ids?](https://www.eclemma.org/jacoco/trunk/doc/classids.html)
   
   
![4](https://user-images.githubusercontent.com/49934421/125169241-db674e00-e1db-11eb-89c4-e7820dead48d.png)
   
   As you can see from the figure below, The `Demo` class is not linked to the 
corresponding coverage report page. It means there is a class id mismatch 
between the class used at runtime and the class provided to create the report.
   
   In addition, you can see the name of the `Demo` class has changed. This is 
due to PowerMock modifying the Demo class at runtime and Jacoco testing it but 
has been modified.
   


-- 
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