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-5851) Inconsistent code coverage shown for LogicalPreparedStatement40
Date Tue, 17 Jul 2012 23:48:34 GMT

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

Bryan Pendleton commented on DERBY-5851:

That additional coverage sounds great! Are you intending to attach an additional
patch to this issue for those other three tests? Or do you think it would be
clearer to deal with them in separate JIRA issues?

> Inconsistent code coverage shown for LogicalPreparedStatement40
> ---------------------------------------------------------------
>                 Key: DERBY-5851
>                 URL: https://issues.apache.org/jira/browse/DERBY-5851
>             Project: Derby
>          Issue Type: Bug
>            Reporter: Mohamed Nufail
>            Assignee: Mohamed Nufail
>            Priority: Minor
>         Attachments: derby-5851-CPdecorator.patch
> I tried running org.apache.derbyTesting.functionTests.tests.jdbc4.PreparedStatementTest
with a connectionCPDecorator in a JDBC4 environment. So this should actually run the test
with LogicalPreparedStatement40 statements. 
> But in code coverage report methods such as setNClob show no coverage in LogicalPreparedStatement40
class. But in PreparedStatement40 class all these methods are shown as covered. Actually those
method calls should go to PreparedStatement40 through LogicalPreparedStatement40. But it is
not shown in emma code coverage report.

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