depending on order of tests is a bad idea. What if the insert record test works and then the delete record test fails? You now have extra records in your database.
One strategy is to use/abuse the transaction management system of your database. Do your inserts etc, then roll back the transaction, never committing the record to the database. Another strategy is to use something like DBUnit. Create some clean state of database, load some sample data into memory and run your tests against that. I'm sure there are others, but unit tests should be atomic and shouldn't depend on other tests. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
