[
https://issues.apache.org/jira/browse/DERBY-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410383#comment-13410383
]
Knut Anders Hatlen commented on DERBY-5851:
-------------------------------------------
org.apache.derbyTesting.junit.JDBCDataSource does some class loader magic in
its getDataSourceObject() method, which is where the ConnectionPoolDataSource
instance is created by the test framework. Not sure if that could cause any
confusion. (I'm not even sure why the class loader magic is needed. Perhaps
it's there to support the upgrade tests, where we need to load a different
version of the data source class than the one found on the system class path?)
> 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
