Absolutely - the "making a seperate DB" is all wrapped in "django-admin.py test" or "./manage.py test" - which does a number of things for you. You don't have to use that at all - and just running standard python unit tests will work against your system. You'll need to set up your environment to use the right "django" bits - the same as you would from using any other general python script external to the webserver, but it works just fine.
-joe On Tue, Mar 25, 2008 at 7:44 AM, Jeff Gentry <[EMAIL PROTECTED]> wrote: > As a relative newcomer to Django, I recently starting looking at how best > to implement unit tests for my app. I came across this page: > http://www.djangoproject.com/documentation/testing/ > as well as a couple of other examples online. > > If I'm understanding things correctly, the unit testing framework creates > a temporary DB separate from the main DB for the purpose of running the > tests, which is then removed afterwards. For my situation, that falls > somewhere between impractical and impossible - OTOH, I do all of my > development using a sandbox DB which I very much would not mind if the > unit tests worked against. > > Is it possible (and if so, how?) to point the unit tests at my sandbox DB? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---