[
https://issues.apache.org/jira/browse/DERBY-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414578#comment-13414578
]
Mohamed Nufail commented on DERBY-5851:
---------------------------------------
Yes, it does work. The code coverage report shows the method as covered in both
PreparedStatement40 and LogicalPreparedStatement40 when an exception is not
thrown. So it looks like the problem is related to throwing exceptions. But
even when an exception was thrown, method was shown as covered in
PreparedStatement40.
> 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
