[
https://issues.apache.org/jira/browse/DERBY-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713428#comment-13713428
]
ahsan shamsudeen commented on DERBY-6291:
-----------------------------------------
Hi,
I got following results in my environment.
C:\Users\Rila\workspace\derby>ant -Dderby.junit.testclass=org.apache.derbyTestin
g.functionTests.tests.jdbcapi.CallableTest junit-single
Unable to locate tools.jar. Expected to find it in C:\Program Files\Java\jre7\li
b\tools.jar
Buildfile: C:\Users\Rila\workspace\derby\build.xml
junit-init-nocp:
[mkdir] Created dir: C:\Users\Rila\workspace\derby\junit_20130719_1227\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: 52, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 24.
454 sec
BUILD SUCCESSFUL
Total time: 26 seconds
> 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 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
