Best way to create / drop a database before / after integration testing on a Maven/Junit/DBUnit project?

Question

I've seen some people use the maven-sql-plugin to do this. But it seems like a task that is better suited for DBUnit....perhaps at the beginning of an entire test suite.

What's the best practice here?

Answer 1

I use the Maven SQL Plugin

You're much better off using it and making sure that you create and populate before your tests and then drop after your tests. You'll also want to use create or replace, or drop if exists in your creation script (assuming your database supports it) in the event that a test fails and leaves the database in some inconsistent state.