Browse files

Fixed #6298 - Added sample settings file to run the Django test suite…

… (SQLite). Thanks, Eric Holscher.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 2164e13 commit c8fa1100930e9741848160fa1fd516e2eb315018 @jezdez jezdez committed Feb 23, 2010
Showing with 37 additions and 0 deletions.
  1. +14 −0 docs/internals/contributing.txt
  2. +23 −0 tests/
@@ -826,6 +826,20 @@ following is a minimal settings file that can be used to test SQLite::
+As a convenience, this settings file is included in your Django
+distribution. It is called ``test_sqlite`, and is included in
+the ``tests`` directory. This allows you to get started running
+the tests against the sqlite database without doing anything on
+your filesystem. However it should be noted that running against
+other database backends is recommended for certain types of test
+To run the tests with this included settings file, ``cd``
+to the ``tests/`` directory and type:
+.. code-block:: bash
+ ./ --settings=test_sqlite
If you're using another backend, you will need to provide other details for
each database:
@@ -0,0 +1,23 @@
+# This is an example test settings file for use with the Django test suite.
+# The 'sqlite3' backend requires only the ENGINE setting (an in-
+# memory database will be used). All other backends will require a
+# NAME and potentially authentication information. See the
+# following section in the docs for more information:
+# The different databases that Django supports behave differently in certain
+# situations, so it is recommended to run the test suite against as many
+# database backends as possible. You may want to create a separate settings
+# file for each of the backends you test against.
+ 'default': {
+ 'ENGINE': 'django.db.backends.sqlite3'
+ },
+ 'other': {
+ 'ENGINE': 'django.db.backends.sqlite3',
+ 'TEST_NAME': 'other_db'
+ }

0 comments on commit c8fa110

Please sign in to comment.