Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 10 Jul 2012 13:51:34 +0000 (UTC)
From: "Bryan Pendleton (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1861826926.28207.1341928294841.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <873571811.20309.1341768638411.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (DERBY-5851) Inconsistent code coverage shown
 for LogicalPreparedStatement40
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Bryan Pendleton commented on DERBY-5851:
----------------------------------------

You could try increasing the Emma logging level: http://emma.sourceforge.net/faq.html#q.verbose
to see if there is a warning from the Emma libraries that perhaps we are overlooking?

                
> 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
>            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