db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-5817) Add support for the JaCoCo code coverage tool
Date Wed, 06 Feb 2013 20:43:13 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kristian Waagan closed DERBY-5817.

I was suspecting that JaCoCo was slower than EMMA, but the results from a new test disagrees.

Here's what I saw from runs on a Windows Vista machine:
 o ant junit-all: ~107 minutes
 o ant emma-all: ~135 minutes
 o ant jacoco-junit: ~134 minutes

The times for EMMA and JaCoCo are comparable, but there are some differences (EMMAs instrumentation
step, the JaCoCo target doesn't build a report - use ant jacoco-complete for that).
I did see some warnings where files couldn't be deleted immediately, so it appears we still
have issues in the tests where resources aren't closed timely or we otherwise do concurrent
access on files.

Closing the issue.
> 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:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For:
>         Attachments: derby-5817-1a-jacoco_support.diff, derby-5817-1b-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
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message