I've been experimenting with the new test frameworks, and am very excited about their potential.
I've hit a snag, and am wondering if it reveals a flaw in the current management.py, or if there is something I don't understand yet (most likely the latter). Russ's test runner uses management.syncdb() to create the test database. I've hooked the post_syncdb signal to create my initial data. It works great. I've also tried Jason's nose-django plugin, and it uses management.install(app) to create the test database. This doesn't fire a signal I can hook, so I wasn't able to create my initial data. But the difference between the two made me wonder if management.py could use some clarification. Which is the proper method to create the database? Do we need both? If so, should both fire the same event so that initial data can be created in a single way? Sorry to have so many questions and so few answers. Perhaps there's a simple path here that I have not found? --Ned. -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
