mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-07-05 18:29:11 +00:00
Code Issues 32 Releases Wiki Activity

[soc2009/multidb] Updated testing documentation for the new settings, also updated the TODO

Browse Source 
git-svn-id: http://code.djangoproject.com/svn/django/branches/soc2009/multidb@11082 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Alex Gaynor 2009-06-19 02:19:37 +00:00
parent 4f199d099c
commit 61db8d6b97
2 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
TODO.txt
View File

@ -9,7 +9,6 @@ that need to be done. I'm trying to be as granular as possible.
``settings.DATABASES``. This includes the following locations ``settings.DATABASES``. This includes the following locations
* ref/settings -- needs to be upddated for TEST_* * ref/settings -- needs to be upddated for TEST_*
* topics/testing -- needs update for the TEST_* settings, plus test refactor
The remaining items will be fixed as the code for them enters the code base. The remaining items will be fixed as the code for them enters the code base.

8
docs/topics/testing.txt
View File

@ -287,8 +287,8 @@ By default this test database gets its name by prepending ``test_`` to the
value of the ``DATABASE_NAME`` setting. When using the SQLite database value of the ``DATABASE_NAME`` setting. When using the SQLite database
engine the tests will by default use an in-memory database (i.e., the database engine the tests will by default use an in-memory database (i.e., the database
will be created in memory, bypassing the filesystem entirely!). If you want to will be created in memory, bypassing the filesystem entirely!). If you want to
use a different database name, specify the :setting:`TEST_DATABASE_NAME` use a different database name, specify ``TEST_DATABASE_NAME`` in the dictionary
setting. for any given database in :setting:`DATABASES`.
Aside from using a separate database, the test runner will otherwise use all of Aside from using a separate database, the test runner will otherwise use all of
the same database settings you have in your settings file: the same database settings you have in your settings file:
@ -301,8 +301,8 @@ account has sufficient privileges to create a new database on the system.
For fine-grained control over the For fine-grained control over the
character encoding of your test database, use the character encoding of your test database, use the
:setting:`TEST_DATABASE_CHARSET` setting. If you're using MySQL, you can also ``TEST_DATABASE_CHARSET`` option. If you're using MySQL, you can also
use the :setting:`TEST_DATABASE_COLLATION` setting to control the particular use the ``TEST_DATABASE_COLLATION`` option to control the particular
collation used by the test database. See the :ref:`settings documentation collation used by the test database. See the :ref:`settings documentation
<ref-settings>` for details of these advanced settings. <ref-settings>` for details of these advanced settings.