After `testFOO` method call test case flushes all data in database. So if you want to add some logic at this stage - flushing procedure may take a lot of time and you will get no speed improvements.
On Oct 14, 5:18 am, Simon Litchfield <[EMAIL PROTECTED]> wrote: > Reloading of fixtures for each test gets painful when the fixtures get > big. > > Maybe we could continue to have TestCase.fixtures as a list of > 'variable' fixtures that do definitely need to be reloaded for each > test... and add a new optional attribute, TestCase.static_fixtures, > which would be a list of fixtures that only need to be loaded at the > start of the TestCase. > > I've run into this problem a few times now and this simple improvement > would make tests so much nicer :-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---