Spring lends itself really well to testing, just load the applicationContext.xml file and off it goes. The problem I've found is that any data added during the tests is hard to remove in the teardown method.. Being able to wire in a few sql scripts and such like that would be inserted during setup and teardown would be a nice means of doing things. Thats where I see the benefit, being able to add a sql scripts as maven properties rather than loading them in a TestCase.
It could well be the penny hasn't dropped with my JUnit knowledge but it does seem a little tricky. On Fri, 3 Dec 2004 11:48:25 -0500, Matt Sgarlata <[EMAIL PROTECTED]> wrote: > ----- Original Message ----- > From: "Mark Lowe" <[EMAIL PROTECTED]> > To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]> > Sent: Friday, December 03, 2004 5:43 AM > Subject: Re: [OT] Test generation > > > I'd really like to find a maven configable way for defining fixtures > > for spring, so the db is setup cleanly on each setup, and removed on > > each teardown. > > What would be the benefit of defining the test fixtures in Maven over > specifying them directly in a Spring test context? > > > Mark > > Matt > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
