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 02:50:35 GMT

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

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

I tried running 'ant -verbose' to see if I could better understand how the emma-single
target works. I've pasted the output of the instrumented JUnit invocation below.

It's interesting, to me, that we appear to have *both* sets of Derby classes in the
classpath: the instrumented derbyrun.jar comes first, and then my normal sane jars
come afterward (although derbyTesting.jar comes before the instrumented derbyrun.jar)

Is this how it is supposed to look? Or should I *only* have the instrumented derbyrun.jar
in my path?

Execute:Java13CommandLauncher: Executing 'java' with arguments:
'-Dderby.dummy.prop=X'
'-Xmx512m'
'-Dderby.tests.jacoco.agent=-Dderby.dummy.prop=X'
'-Demma.verbosity.level=silent'
'-classpath'
'/home/bpendleton/src/derby/trunk/tools/java/emma.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyTesting.jar:/home/bpendleton/src/derby/trunk/jars/emma/lib/derbyrun.jar:/home/bpendleton/src/derby/trunk/tools/java/junit.jar:/home/bpendleton/src/derby/trunk/tools/java/jakarta-oro-2.0.8.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyrun.jar:/home/bpendleton/src/derby/trunk/jars/sane/derby.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbytools.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbynet.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyclient.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyLocale_de_DE.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyLocale_es.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyLocale_fr.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyLocale_it.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyLocale_ja_JP.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyLocale_ko_KR.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyLocale_pt_BR.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyLocale_zh_CN.jar:/home/bpendleton/src/derby/trunk/jars/sane/derbyLocale_zh_TW.jar:/home/bpendleton/tools/apache-ant-1.7.1/lib/ant-launcher.jar:/home/bpendleton/tools/apache-ant-1.7.1/lib/ant.jar:/home/bpendleton/tools/apache-ant-1.7.1/lib/ant-junit.jar'
'org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner'
'org.apache.derbyTesting.functionTests.tests.jdbc4.PreparedStatementTest'

                
> 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

       

Mime
View raw message