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 Wed, 11 Jul 2012 13:32:34 GMT

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

Bryan Pendleton commented on DERBY-5851:

Indeed, I had CLASSPATH set. Good catch!

Nufail, here's a few other suggestions that might be worth trying:

1) Can you identify any pattern in which LogicalPreparedStatement40 methods are
correctly instrumented, and which are not? Try putting a 'System.out.println' at the
front of every single method in LogicalPreparedStatement40, so that you can manually
determine which methods are being executed by PreparedStatementTest, and which are
not, and then compare your findings with the Emma report to see which methods it's missing.

2) Once you've done that, try the same thing with JaCoCo. Do both tools miss the same
set of methods? Or is one tool missing a different set than the other?

3) We could try asking on either the Emma or JaCoCo lists for suggestions on how to
diagnose a problem such as this. Perhaps those tools have additional internal debugging
we can enable, to gather more information about the instrumentation and reporting phases
to see if we can figure out where the methods are being dropped.

> 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