You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2012/06/14 10:37:42 UTC
[jira] [Updated] (DERBY-5817) Add support for the JaCoCo code
coverage tool
[ https://issues.apache.org/jira/browse/DERBY-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-5817:
-----------------------------------
Attachment: derby-5817-1a-jacoco_support.diff
Attaching patch 1a, which adds support for JaCoCo.
The change in build.xml enables JaCoCo, and the change in BaseTestCase ensure that JaCoCo will also be enabled in spawned Java processes (as for EMMA).
There are two new top-level targets, based on junit-all and junit-single:
jacoco-all
jacoco-single
You have to download JaCoCo and place the two jar files jacocoant.jar and jacocoagent.jar in tools/java. The targets above will complain if these files are missing.
When running jacoco-all I'm still seeing one error, which appears to be a problem with ASM, which is used by JaCoCo. I'll see if I can find any more information on this issue. The error doesn't cause the run to be aborted, and the coverage data appears ok.
The report ends up in junit_{timestamp}/coverage-report.
Patch ready for review.
> Add support for the JaCoCo code coverage tool
> ---------------------------------------------
>
> Key: DERBY-5817
> URL: https://issues.apache.org/jira/browse/DERBY-5817
> Project: Derby
> Issue Type: Task
> Components: Miscellaneous, Test
> Affects Versions: 10.10.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments: derby-5817-1a-jacoco_support.diff
>
>
> Add support for the JaCoCo code coverage tool ([1]).
> While we are currently relying on EMMA for code coverage, the tool isn't being maintained. It works nicely for the time being, but having additional support for a tool that's being actively developed and maintained would be nice.
> [1] http://www.eclemma.org/jacoco/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira