On 26/04/2012 05:31, Bhuvnesh Pratap wrote:
Hey People !
Though I know this has nothing to do with the working of the the
JBehave and Co. but any BDD/TDD
strategy must make sure that it leaves the database clean after every
run of a test case/scenario.
As of now I have been using the create snapshot/restore snapshot
methodology to maintain a clean
state for the database after every run of the scenario(What I am
testing is a web application and SQLserver
makes life easy here) .
I am keen to hear what other people are doing to keep the DB clean
since RDBMS like MySQL and other
probably don't have a snapshot feature as far as I know. Moreover are
their any ground rule for doing it ?
The usual way is to use a framework like DBunit which can preload data
into an RDBMS, and then delete it automatically at the end of the run.
I'm sure there's any number of them around but DBunit is the one I have
experience of.
Rob
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
