On 15 Apr 2009, at 19:44, George Vilches wrote: > As someone who's managed to hard-crash the Python interpreter while > building tests for the test suite, they most definitely should be in > the setup phase. It's the only way to ensure that right before your > test starts, no matter what horrible things happened previously, your > test DB will stay intact.
I sort of see what you mean by that, but bear in mind that all the flush stage does is truncate most of the tables, so you could still theoretically do damage to your database prior to running tests that this wouldn't undo (such as changing table structures or altering the content types data). Obviously it will help if by 'horrible things' you mean inserting broken or unwanted data into your model tables, but it strikes me that the solution to that is to fix the code that's doing it! -- Sean Legassick [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
