To my knowledge the only open code coverage tool being maintained is JaCoCo. We were going to try that for OpenJFX. The current build doesn't work on Java 8 though :-/
Richard On May 18, 2013, at 8:49 AM, Alan Bateman <alan.bate...@oracle.com> wrote: > On 18/05/2013 11:26, Richard Warburton wrote: >> Hi, >> >> I'm currently helping Steve Poole run an openjdk test-fest in Krakow. The >> goal of the event to be incrementally improving test coverage in Openjdk. >> One of the issues that has cropped up is the lack of available coverage >> reports in openjdk. >> >> When this has been previously discussed it was commented there is already >> internal code coverage tooling, but this information wasn't publicly >> available. Any update or clarification on this situation would be most >> appreciated. >> >> If there is a barrier to making the tooling publicly available then even >> publicly publishing HTML or text reports to provide visibility into the >> situation would be helpful. The results of test runs are already regularly >> posted to this list. >> > In Oracle, the tool that we use is called "jcov", it's proprietary so I can't > point you at anything. Maybe someday it could be proposed to the Code Tool > Projects but I have no knowledge of specific plans on that. > > I wonder if anyone has tried using EMMA or any of the other code coverage > tools out there? At least for the JDK releases in development then one > challenge would be keeping the tool up to the date with the class file > format, another would be taking care when instrumenting very core classes > that are used early in VM startup. It's the same challenge that profiles and > other tools that do bytecode instrumentation have used on a JDK version that > is still in development. > > -Alan. > > > >