Im using jacoco as above. Previously it was working fine with tomcat 7 and java 8 and I was getting code coverage information. But now I had to upgrade to tomcat 8.0.26.08 and Java 1.8.0_131-b11. Now I'm always getting zero coverage. Can anyone help pls? Is there any log or something which I use for troubleshooting Thanks, Angel |
DumpCoverage cover = new DumpCoverage();
cover.createCoverageDump(tcpserver, port, coverageResultPath + "/" + coverageDumpFileName, append, retryCount);
// create the coverage resport
final ReportGenerator generator3 = new ReportGenerator(coverageResultPath, coverageDumpFileName, classesDirectory,
sourcesDirectory);
generator3.create();
Im using jacoco-maven plugin 0.7.9 for writing the reports.
I can get the list of classes and functions, only problem is that it remains the same with 0 coverage even after performing some actions on the webapplication
This was working before with tomcat 7 previously.
I dont get any sort of warning or error message. Is there any sort of logs I can check for it?
Please let me know if there is any compatibility issues with tomcat 8
Thank you,
Angel
Thanks for your reply.
I'm using the latest version of jacoco 0.7.9.
I made sure the exec file generated is not empty its around 50MB,
I write the reports to html forms using the lines below:DumpCoverage cover = new DumpCoverage();
cover.createCoverageDump(tcpserver, port, coverageResultPath + "/" + coverageDumpFileName, append, retryCount);// create the coverage resport
final ReportGenerator generator3 = new ReportGenerator(coverageResultPath, coverageDumpFileName, classesDirectory,
sourcesDirectory);
generator3.create();Im using jacoco-maven plugin 0.7.9 for writing the reports.
I can get the list of classes and functions, only problem is that it remains the same with 0 coverage even after performing some actions on the webapplication
This was working before with tomcat 7 previously.
I dont get any sort of warning or error message. Is there any sort of logs I can check for it?
Please let me know if there is any compatibility issues with tomcat 8