diff options
| author | krishbharadwaj <krishna.bmsce@gmail.com> | 2016-04-06 01:22:34 +0530 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-04-05 21:34:26 -0400 |
| commit | 361cb7a857f1ca69754c0e3a0038097d09508f2c (patch) | |
| tree | 6e0f5a35d1b3cec97250714d0ec508ed93bc51ee | |
| parent | 90ce5d46bf62a74d7c78a61c1a7bab64f7cb1735 (diff) | |
Fixed #26448 -- Added details for running tests with a different database backend.
| -rw-r--r-- | docs/internals/contributing/writing-code/unit-tests.txt | 9 | ||||
| -rw-r--r-- | docs/intro/contributing.txt | 5 |
2 files changed, 9 insertions, 5 deletions
diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt index 2cbbd30dd4..b4ec5780cf 100644 --- a/docs/internals/contributing/writing-code/unit-tests.txt +++ b/docs/internals/contributing/writing-code/unit-tests.txt @@ -50,10 +50,11 @@ Having problems? See :ref:`troubleshooting-unit-tests` for some common issues. Using another ``settings`` module --------------------------------- -The included settings module allows you to run the test suite using -SQLite. If you want to test behavior using a different database (and -if you're proposing patches for Django, it's a good idea to test -across databases), you may need to define your own settings file. +The included settings module (``tests/test_sqlite.py``) allows you to run the +test suite using SQLite. If you want to run the tests using a different +database, you'll need to define your own settings file. Some tests, such as +those for ``contrib.postgres``, are specific to a particular database backend +and will be skipped if run with a different backend. To run the tests with different settings, ensure that the module is on your ``PYTHONPATH`` and pass the module with ``--settings``. diff --git a/docs/intro/contributing.txt b/docs/intro/contributing.txt index 1c6d321375..379db4a230 100644 --- a/docs/intro/contributing.txt +++ b/docs/intro/contributing.txt @@ -273,7 +273,10 @@ passing tests. Skipped tests are typically due to missing external libraries required to run the test; see :ref:`running-unit-tests-dependencies` for a list of dependencies and be sure to install any for tests related to the changes you are making (we -won't need any for this tutorial). +won't need any for this tutorial). Some tests are specific to a particular +database backend and will be skipped if not testing with that backend. SQLite +is the database backend for the default settings. To run the tests using a +different backend, see :ref:`running-unit-tests-settings`. Once the tests complete, you should be greeted with a message informing you whether the test suite passed or failed. Since you haven't yet made any changes |