db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1097) Add tests for Statement.isClosed()
Date Sun, 12 Mar 2006 21:22:39 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1097?page=all ]

Kristian Waagan updated DERBY-1097:

    Attachment: StatementTest.java

Updated preliminary tests for Statement.isClosed(). Feedback is appreciated, but the files
are *not* ready for commit (awaiting review and need to see where the JUnit infrastructure
discussion lands).

> 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:
>  Environment: JDBC4 / JDK 1.6
>     Reporter: Kristian Waagan
>     Assignee: Kristian Waagan
>  Attachments: StatementTest.java, StatementTestSetup.java
> 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:
For more information on JIRA, see:

View raw message