On 6/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Is it appropriate to have a test that requires sqlite, or should tests > always use the database engine(s) specified in settings?
Tests should always use the database engines in settings. > If they should always use the engines in settings, when needing > multiple databases, is it appropriate to kill the test with an error > specifying how the settings must be set up for the test to run when the > needed databases are not defined? Or should the test create the > databases it needs using the default engine? It should work the way it works currently: It should attempt to create a test database (or databases). If any database of that name already exists, it should display a confirmation message. (Does this answer your question?) > Are there any objections to my adding setup/teardown support for model > tests? (Basically: run module.setup() if defined before running tests; > run module.teardown() if defined after running tests.) Yeah, I'm a bit hesitant to do this -- only because the model tests double as our "model examples" documentation, and for that use it's essential that the examples be clear. > Are there any objections to my extending the test db setup/teardown in > runtests to include creating and destroying test dbs for all dbs > defined in DATABASES? I think I answered this question above, but if I didn't, re-ask it. :) Adrian -- Adrian Holovaty holovaty.com | djangoproject.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 -~----------~----~----~----~------~----~------~--~---
