You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "William R. Speirs (JIRA)" <ji...@apache.org> on 2011/07/29 03:28:09 UTC
[jira] [Commented] (DBUTILS-53) Set Derby up as a unit test
database
[ https://issues.apache.org/jira/browse/DBUTILS-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072641#comment-13072641 ]
William R. Speirs commented on DBUTILS-53:
------------------------------------------
I've noticed that the unit tests currently don't leverage JUnit 4 or mocking frameworks like Mockito. These unit tests also don't cover the batch, query, or update methods. As a large part of the purpose of this library is to ensure all resources are properly closed, it would make sense to ensure this is being done via the unit tests.
I guess what I'm proposing is to use Mockito to mock Connection, PreparedStatement, and ResultSet and then ensure that the close() methods are called on each. Thoughts?
> Set Derby up as a unit test database
> ------------------------------------
>
> Key: DBUTILS-53
> URL: https://issues.apache.org/jira/browse/DBUTILS-53
> Project: Commons DbUtils
> Issue Type: Task
> Reporter: Henri Yandell
>
> Or hsqldb. I used Derby for Taglibs to test the sql tags and it worked well enough.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira