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-6291) Improve code coverage of org.apache.derby.iapi.jdbc.BrokeredCallableStatement
Date Fri, 19 Jul 2013 01:33:46 GMT

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

Bryan Pendleton commented on DERBY-6291:

Hi Ahsan,

The patch applies and builds cleanly for me. But when I run it, with:

    ant -Dderby.junit.testclass=org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest

I get:

    [junit] Running org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest
    [junit] Tests run: 440, Failures: 2, Errors: 93, Skipped: 0, Time elapsed: 57.414 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest FAILED

What are the results in your environment?



> Improve code coverage of  org.apache.derby.iapi.jdbc.BrokeredCallableStatement
> ------------------------------------------------------------------------------
>                 Key: DERBY-6291
>                 URL: https://issues.apache.org/jira/browse/DERBY-6291
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC
>            Reporter: ahsan shamsudeen
>            Assignee: ahsan shamsudeen
>            Priority: Minor
>              Labels: derby_triage10_11
>         Attachments: DERBY-6291.patch
> According to code coverage analysis, org.apache.derby.iapi.jdbc.BrokeredCallableStatement
> exercised poorly by of our regression tests. The current coverage report for this class
can be found at http://dbtg.foundry.sun.com/derby/test/coverage/_files/a9.html
> This task is to investigate this class, and either remove the unused code, or add
> regression test that exercise the code, as appropriate.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message