I use either the ant <SQL> task or DBUnit to reset my database to a consistent state. I find that to be the only way to keep sane with all these various tests...

Here is an example:

<target name="exportOptOutEmailsToBrowser"> <dbunit driver="${sql.jdbcdriver}" url="${sql.url}" userid="${sql.username}" password="${sql.password}"> <operation type="MSSQL_REFRESH" src="data/exportEmailsToBrowser.xml" format="flat"/> </dbunit>

<testSpec name="exportOptOutEmailsToBrowser"> &sharedConfiguration; <steps> &invokeHome; <clickbutton stepid="Click link to Go To Export Email Addresses" label="Export Email Addresses"/> <verifytitle stepid="Make sure we are on the Export Page" text="Export Email Addresses"/> &verifyNoError; <setinputfield stepid="set download type to browser window" name="downloadtype" value="1" /> <setinputfield stepid="set optout radio button" name="exportType" value="optout" /> <clickbutton stepid="Click link to Export Email Addresses" label="Export Email Addresses"/> <verifytext stepid="Make sure we have not exported opted out" text="2exp...@test.com"/> <not stepid="make sure opted out people are not included"> <verifytext stepid="Make sure we exported good data" text="1exp...@test.com"/>

<verifytext stepid="Make sure we exported good data" text="3exp...@test.com"/> </not> </steps> </testSpec> </target>

The dbunit just resets everything, and then loads my data.

Eric Pugh