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

ahsan shamsudeen commented on DERBY-6291:
-----------------------------------------

Hi,

Now I have run the new version of the CallableTest.java  and got the same 
result. Then I change some prepareCall() procedures which failed to run. 
Consequently, the number of errors get reduced. Here is the latest output .

C:\Users\Rila\workspace\derby> ant -Dderby.junit.testclass=org.apache.derbyTesti
ng.functionTests.tests.jdbcapi.CallableTest junit-single
Buildfile: C:\Users\Rila\workspace\derby\build.xml

junit-init-nocp:
    [mkdir] Created dir: C:\Users\Rila\workspace\derby\junit_20130721_1413\testo
ut

junit-init:

emit-junit-classpath-jars:

emit-junit-classpath:
     [echo] Running with classes or user specified classpath: C:\Users\Rila\work
space\derby/classes
     [echo] CLASSPATH (environment variable): ${env.CLASSPATH}

junit-single:
    [junit] Running org.apache.derbyTesting.functionTests.tests.jdbcapi.Callable
Test
    [junit] Tests run: 440, Failures: 2, Errors: 53, Skipped: 0, Time elapsed: 5
5.197 sec
    [junit] Test org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTes
t FAILED

BUILD SUCCESSFUL
Total time: 59 seconds


As I understood, What causes this errors is , I din't call suitable 
prepareCall() procedure in above failed methods. But, Its hard to find an 
existing procedure which suits above methods. For Example,

public final void registerOutParameter(int paramIndex,int sqlType,String 
typeName)throws SQLException
{
                
        getCallableStatement().registerOutParameter( paramIndex, sqlType, 
typeName);
}

public final boolean getBoolean(int parameterIndex)throws SQLException
{
                return getCallableStatement().getBoolean( parameterIndex);
}

public final <T> T getObject(int parameterIndex, Class<T> type)throws 
SQLException
{
                return ((EngineCallableStatement) getCallableStatement())
                        .getObject(parameterIndex, type);
}

Do any existing prepareCall() procedures suits above methods ? 

Thanks,
Ahsan
                
> 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, setIntPatch.txt
>
>
> According to code coverage analysis, 
> org.apache.derby.iapi.jdbc.BrokeredCallableStatement is 
> 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

Reply via email to