On 4/19/07, jararaca <[EMAIL PROTECTED]> wrote: > > > The most likely cause I can think of is that your test extends > > unittest.TestCase, not django.test.TestCase. > > Yes, you're right indeed. I have corrected this but still the fixture > is not found + the tests now take 3 minutes instead of half a second. > I think I'll stick to the "initial_data" variant.
The reason for this is that the tables are completely flushed after each test, so each test is run with a clean database. Flushing is an expensive operation, so the tests slow down significantly. However, tests extending unittest.TestCase can operate differently depending on execution order. Flushing prevents this kind of problem. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
