1 Answer
- Newest
- Most votes
- Most comments
3
JaCoCo uses a value called “classId” to compare java classes used at runtime and at analysis time. If these classes are different, the classId values are different, and JaCoCo does not compare them, thus the 0% coverage.
Source: https://www.eclemma.org/jacoco/trunk/doc/classids.html
You can check the Blu Age L3 Workshop for CardDemo to help you with fixing the 0% coverage you observe, because it depends on your own configuration.
https://catalog.workshops.aws/aws-blu-age-l3-certification-workshop/en-US/automation/execute, in insert “0% Coverage for JaCoCo”.
answered a month ago
Relevant content
- Accepted Answerasked a month ago
- Accepted Answerasked a month ago
- Accepted Answerasked a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 25 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago