Opened 18 years ago
Closed 18 years ago
#4226 closed (fixed)
Running Django unit tests requires DATABASE_NAME setting despite what the docs. say
Description ¶
The 'Contributing to Django' docs say that DATABASE_ENGINE
, DATABASE_USER
, and DATABASE_PASSWORD
settings are required to running Django's unit tests, but DATABASE_NAME
is also required.
$ ./runtests.py --settings=settings Traceback (most recent call last): File "./runtests.py", line 154, in <module> django_tests(int(options.verbosity), args) File "./runtests.py", line 127, in django_tests failures = run_tests(test_models, verbosity, extra_tests=extra_tests) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/test/simple.py", line 81, in run_tests create_test_db(verbosity) File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/test/utils.py", line 62, in create_test_db cursor = connection.cursor() File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/django/db/backends/postgresql/base.py", line 71, in cursor raise ImproperlyConfigured, "You need to specify DATABASE_NAME in your Django settings file." django.core.exceptions.ImproperlyConfigured: You need to specify DATABASE_NAME in your Django settings file.
Change History (3)
by , 18 years ago
Attachment: | contributing_db_name.diff added |
---|
comment:1 by , 18 years ago
Summary: | [patch] Running Django unit tests requires DATABASE_NAME setting → Running Django unit tests requires DATABASE_NAME setting despite what the docs. say |
---|---|
Triage Stage: | Unreviewed → Ready for checkin |
comment:2 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Added
DATABASE_NAME
to section on running unit tests