db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2514) convert lang/closed.java to junit
Date Sat, 14 Apr 2007 14:41:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488868

Myrna van Lunteren commented on DERBY-2514:

I looked a bit more closely at closed test, and I think there may be 2 small areas that are
not covered by the testing of ClosedObjectTest:

- DERBY-62 test case
    I undid the changes for DERBY-62 (revision 110114) to iapi/error/StandardException and
impl/jdbc/EmbedSQLException, and indeed, the closed.java test shows a difference, but the
problem is not detected by ClosedObjectTest
- I don't see ClosedObjectTest testing reading of DatabaseMetaData obtained earlier, after
a connection is closed. 
I don't see an easy/pretty way to put either of these two small test cases into the ClosedObjectTest.

Maybe it's best to create a separate junit test with just those two small issues. Or can they
be put into some other (which) test? Maybe the DatabaseMetaData case can be put into DatabaseMetaDataTest?
But I don't see a good place for the DERBY-62 test case.

> convert lang/closed.java to junit
> ---------------------------------
>                 Key: DERBY-2514
>                 URL: https://issues.apache.org/jira/browse/DERBY-2514
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>         Environment: convert lang/closed.java to junit
>            Reporter: Ramandeep Kaur
>         Assigned To: Ramandeep Kaur
>            Priority: Minor
>             Fix For:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message