[ http://issues.apache.org/jira/browse/DERBY-1097?page=all ]
Kristian Waagan updated DERBY-1097:
-----------------------------------
Attachment: StatementTest.java-v1
StatementTestSetup.java-v1
Updated tests to run with the new base JUnit test classes. Had to rename files
because I can't delete the old ones; 'StatementTest.java-v1' and
'StatementTestSetup.java-v1'. Tests are not yet added to a suite. They could be
added to jdbc4 suite, but then they would only be run under DerbyNetClient, not
embedded.
* Tests passed for embedded.
* Tests cannot be run under DerbyNet, because JCC (at least my version) does
not support JDBC4 (you'll get an AbstractMethodError).
* Tests fail when run unmodified under DerbyNetClient (see error below). This
is because of (another) bug in the exception or stored procedure handling. If
offending test code is removed in StatementTestSetup.setUp (lines 61-70), tests
pass also under DerbyNetClient.
Tests ready for review/commit.
> There was 1 error:
> 1)
> org.apache.derbyTesting.functionTests.tests.jdbc4.StatementTestjava.sql.SQLException:
> DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ009, SQLERRMC: Use of
> CallableStatement required for stored procedure call or use of output
> parameters: call SYSIBM.SQLCAMESSAGE(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
> Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error: SQLCODE:
> -1, SQLSTATE: XJ009, SQLERRMC: Use of CallableStatement required for stored
> procedure call or use of output parameters: call
> SYSIBM.SQLCAMESSAGE(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
> ... 8 more
> FAILURES!!!
> Tests run: 0, Failures: 0, Errors: 1
Test Failed.
*** End: StatementTest jdk1.6.0-beta2 DerbyNetClient 2006-03-17 14:41:58 ***
> Add tests for Statement.isClosed()
> ----------------------------------
>
> Key: DERBY-1097
> URL: http://issues.apache.org/jira/browse/DERBY-1097
> Project: Derby
> Type: Sub-task
> Components: Test
> Versions: 10.2.0.0
> Environment: JDBC4 / JDK 1.6
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: StatementTest.java, StatementTest.java-v1,
> StatementTestSetup.java, StatementTestSetup.java-v1
>
> Add tests for Statement.isClosed() (implemented as part of DERBY-953).
> The tests are already written, but because of some "confusion" and diverging
> paths regarding how to get connections when running JUnit tests, they are
> held back.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
