db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5853) Test for methods in BrokeredPreparedStatement
Date Thu, 12 Jul 2012 13:54:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412794#comment-13412794

Bryan Pendleton commented on DERBY-5853:

Perhaps you could ask the JaCoCo community on their mailing list for some suggestions
about how to diagnose this problem. Is there additional logging/tracing in the JaCoCo
tool that we can enable that will help us identify where the coverage information is
being lost?

> Test for methods in BrokeredPreparedStatement
> ---------------------------------------------
>                 Key: DERBY-5853
>                 URL: https://issues.apache.org/jira/browse/DERBY-5853
>             Project: Derby
>          Issue Type: Sub-task
>            Reporter: Siddharth Srivastava
>            Assignee: Siddharth Srivastava
>            Priority: Minor
>         Attachments: brokeredps.patch, pstest.patch
> According to emma code coverage report, several methods of BrokeredPreparedStatement
are uncovered. 
> This issue deals with adding tests for those methods.

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


View raw message