#2333: Add unit test framework for end-user Django applications
---------------------------------+------------------------------------------
Reporter: russellm | Owner: russellm
Status: closed | Component: Unit test system
Version: SVN | Resolution: fixed
Keywords: unit test doctest | Stage: Design decision needed
Has_patch: 1 | Needs_docs: 1
Needs_tests: 0 | Needs_better_patch: 1
---------------------------------+------------------------------------------
Comment (by [EMAIL PROTECTED]):
Replying to [comment:19 russellm]:
> (In [3706]) Refs #2333 - Added a TEST_DATABASE_NAME setting that can be
used to override the 'test_' + DATABASE_NAME naming policy. This setting
is then used in runtests.py to restore the use of 'django_test_db' as the
Django model/regression test database. Thanks to Michael Radziej for the
feedback.
What about `TEST_DATABASE_USER` and `TEST_DATABASE_PASSWORD`, etc.? (I'm
running on a shared host whose only support for databases is one-per-
user.)
--
Ticket URL: <http://code.djangoproject.com/ticket/2333#comment:45>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
