Solved it for now by using the haltonfailure attribute of the sqlunit element on the cleanup step...
The webtest has setup, test, cleanup steps. Setup and cleanup use sqlunit. If the webtest succeeds there's no problem, the database is clean afterwards. If the webtest fails we have a problem, cause the next setup step will break ( record blabla already exists...). In order to get away with this potential problem the webtest becomes: clean with haltonfailure false, setup, test and clean with haltonfailure true. So now this webtest can be rerun in a more robust way... Thanks for the help, avander. A Vander wrote: > > Hope there are some sqlunit guru's out here... :-). > > In order to setup my database, I need to cleanup to tables, say 'person' > and 'adress'. If the test person is still in the db I have to remove all > his adress records. > > I've been looking at the sqlunit manual but it's unclear to me how I can > run the 'remove adresses' step only if I found the person's adress first? > > TIA, Avander; > -- View this message in context: http://www.nabble.com/-sqlunit--how-to-run-tests-conditionnally--tp24755285p25171776.html Sent from the WebTest mailing list archive at Nabble.com. _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
