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?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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?
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.