db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()
Date Wed, 22 Mar 2006 00:57:27 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371366 ] 

Rick Hillegas commented on DERBY-1097:
--------------------------------------

I think that my rototill doesn't affect Kristian's patch. He has written a JUnit test which
uses conventional machinery to get a connection. That is, he did not follow the idiosyncratic
pattern used by the other tests and that's why he was reluctant to wire this into the old
suite. It should be possible to just wire his test into the jdbc40 suite. In fact, that's
the only recommendation I would make. I can take a look at this when I pop off my interrupt
stack.

> 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: DERBY-1097-2a.diff, DERBY-1097-2a.stat, DERBY-1097-2b.diff, 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


Mime
View raw message