Code Coverage

[Richard Warburton]

Hi,

Thanks for the replies everyone.

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.
>

If jcov produces HTML reports - would it be possible to have the reports
from your internal CI builds published?  This would at least improve the
situation even in the absence of jcov being made available.

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.
>

I imagine with sufficient effort Jacoco could be made to work - though I
was hoping to avoid debugging Jacoco with Java 8.  I'll have a look into
this.  At work we've got a patch against Jacoco in order to merge together
the results from different sub module builds in maven, so I'll see if its
possible to use this this same approach in order to make Jacoco work with
merging separate files from different openjdk VMs as Johnathan has
suggested.

regards,

  Richard Warburton

  http://insightfullogic.com
  @RichardWarburto <http://twitter.com/richardwarburto>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/quality-discuss/attachments/20130518/3af3de47/attachment.html