[
https://issues.apache.org/jira/browse/DERBY-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715888#comment-13715888
]
Bryan Pendleton commented on DERBY-6291:
----------------------------------------
Hi Ahsan,
I think that the only methods we should be specifically adding test
cases for are the ones which take "String parameterName" in
their signature, NOT the ones which take "int parameterIndex" or "int i".
That is, I see this JIRA issue as specifically about adding a suite
of test cases which cover the "named parameters" APIs in the
CallableStatement interface, and those are the ones which have
"String parameterName" in their interface.
Does this make sense?
thanks,
bryan
> 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,
> UPDATED-DERBY-6291.patch
>
>
> 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
