- Newest
- Most votes
- Most comments
The issue you're experiencing with the JaCoCo report in the AWS Blu Age L3 Workshop is related to class file mismatches between the execution data and the classes being analyzed. This is why you're seeing all those "Execution data for class X does not match" messages and why you can't see anything in the Service Layer of the report.
This mismatch typically occurs when the class files used during runtime (when the code coverage data was collected) are different from the class files being used during report generation. This could happen for several reasons:
-
The application might have been rebuilt or recompiled between the time the coverage data was collected and when the report was generated.
-
There might be version inconsistencies between the compiled classes in your workspace and the ones that were actually executed.
-
The class files might be coming from different locations or build paths.
To resolve this issue, you could try:
-
Ensuring that you're using the same version of the code for both execution and report generation.
-
Rebuilding the entire project before running the tests and generating the report to ensure consistency.
-
Checking your Tomcat configuration to make sure it's correctly synchronized with your Eclipse workspace.
-
Verifying that all required datasources (jics, bluesam, bac, primary) are correctly configured.
-
Making sure the database server is started and running correctly before executing the tests.
If the problem persists, you might need to clean your project and rebuild it from scratch, as sometimes cached or stale build artifacts can cause unexpected errors in the coverage reporting process.
Sources
AWS Blu Age L3 Workshop - Error on Automation - Execute | AWS re:Post
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
answered a year ago
Relevant content
asked 2 years ago
