How do I unit test jdbc code in java? [closed]

Answer 1

I prefer using EasyMock for testing a not-so-easy-to-test code.

Answer 2

I would say that HSQL is the way to go during your unit tests. The point of your test is to test your jdbc code and make sure it works. Adding custom classes or mocking the jdbc calls can easily hide bugs.

I mostly use mysql and when the tests run the driver class and url is changed to org.hsqldb.jdbcDriver and jdbc:hsqldb:mem:test.

Answer 3

Have a look at JDBDT: http://jdbdt.org

You can use it for database setup and assertions, as an alternative to DBUnit.

Note: I am the author of JDBDT.

Answer 4

You have several options:

• Mock the database with a Mock library, e.g. JMock. The huge drawback of this that your queries and the data will most likely be not tested at all.
• Use a light weight database for the tests, such as HSQLDB. If your queries are simple, this is probably the easiest way to go.
• Dedicate a database for the tests. DBUnit is a good option, or if you are using Maven, you can also use the sql-maven-plugin to set up and tear down the database properly (be careful of dependencies between tests). I recommend this option as it will give you the biggest confidence that the queries work properly with your db vendor.

Sometimes it is necessary and useful to make these tests configurable so that these tests are only executed if the database is available. This can be done with e.g. build properties.

Answer 5

While the way to mock jdbc in your application is of course dependant on how you've implemented your actual jdbc transactions.

If you're using jdbc as is, I'd assume you have written yourself an utility class of sorts to do some tasks in the line of DBUtils.getMetadataFor(String tablename). What this would mean is that you'd have to create a mock of that class and that could be all you need. This would be rather easy solution for you since you apparently already have a series of jdbc related mock objects available. Note that I'm assuming your jdbc code isn't exploded all around the application - if it is, refactor!!!

If you're however using any framework for database handling (like Spring Framework's JDBC Template classes) you can and should mock the interface class using EasyMock or some other equivalent. That way you can have all the power in the world required for easy mocking of the connection.

And last if nothing else works, you can do what others have said already and use DBUnit and/or derby.

Answer 6

That's why you have derby (now called JavaDB) or sqlite -- they are small, simple databases that you can create, load, test against and destroy relatively quickly and simply.