I didn't implement DBunit in each test case because I wanted to avoid: 1.) changing each of the database related test cases to extend from a dbunit base class (reducing my test's coupling to the framework) -and- 2.) I only want to insert the test data once, before a run of integration tests -- I don't want to insert the data before *each* test unless I have to (thus reducing the time it takes to run the integration tests).
I want to make the database set up part of the integration tests as external as possible to the test cases themselves, governed as part of the build process associated with integration tests. -jason -----Original Message----- From: LECAN Damien [mailto:[EMAIL PROTECTED] Sent: Thursday, September 21, 2006 10:58 AM To: Maven Users List Subject: RE: Database Initialization Prior to Testing > I've considered, but rejected, DBunit since the dbunit plugin doesn't > apparently exist for Maven2 Why do you need a maven plugin to use DBUnit ? It's an extension of JUnit, run it as a JUnit test ! It doesn't work ? Damien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
