1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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”.
répondu il y a 2 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 jours
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an