I like to use DBUnit.. DBUnit has a series of Ant tasks that allow you to update the database. This works very well if you have a "test" database where you can delete/modify/insert data to your hearts contents.

Here is an example test.

Ant Script: <target name="exportOptInEmailsToBrowser">

<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="exportOptInEmailsToBrowser"> &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 optin radio button" name="exportType" value="optin" /> <clickbutton stepid="Click link to Export Email Addresses" label="Export Email Addresses"/> <verifytext stepid="Make sure we have a title" text="email id,email,optin"/>

<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 stepid="make sure opted out people are not included"> <verifytext stepid="Make sure we have not exported opted out" text="2exp...@test.com"/> </not> </steps> </testSpec> </target>

exportEmailsToBrowser.xml file for DBUnit:

<dataset>

<EMAIL EMAIL_ID='1' EMAIL='1exp...@test.com' OPTIN='1'/> <EMAIL EMAIL_ID='2' EMAIL='2exp...@test.com' OPTIN='0'/> <EMAIL EMAIL_ID='3' EMAIL='3exp...@test.com' OPTIN='1'/>

</dataset>

This works well for Unit style tests with WebTest.. I only

could get my results into a format that JUnit could use. Or some sort of wrapper JUnit testcase that would call Ant and put the results out in a more Junit friendly format..