db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (DERBY-1097) Add tests for Statement.isClosed()
Date Tue, 15 May 2007 09:43:16 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan reopened DERBY-1097:
------------------------------------


Reopening to set fix version.

> Add tests for Statement.isClosed()
> ----------------------------------
>
>                 Key: DERBY-1097
>                 URL: https://issues.apache.org/jira/browse/DERBY-1097
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Test
>    Affects Versions: 10.2.1.6
>         Environment: JDBC4 / JDK 1.6
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>             Fix For: 10.2.1.6
>
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message