On May 19, 1:34 pm, Daniel Fetchinson <[email protected]> wrote: > If I were you, I would change my testing strategy. I found it to be > much better to test with a test db and make all sorts of mess in that > and not touching my "real" db. You can create/delete/insert/update/etc > in the test db as you like, there is no danger in messing it up. This > will also encourage you to test more and test more crazy scenarios > because you won't be afraid to mess up the "real" db.
Yeah, I didn't mention it, but I am doing that. my test.cfg uses a database that is exclusively set up for testing with. I still want to rollback at the end of each test in order to get back to the beginning state. For example, I have a test that verifies I can insert a row into a table. If I don't rollback or manually delete the row, the second time I run the test, it will fail because of a PK constraint. I don't want to manually wipe out all the entries because it is a hassle to keep updating my teardown method after each new test. So, how can I purge all the data quickly? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
