summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorRamiro Morales <cramm0@gmail.com>2012-12-21 21:59:06 -0300
committerRamiro Morales <cramm0@gmail.com>2012-12-21 21:59:06 -0300
commitd19109fd37e75ccf29d2ca64370102753dbc7c5b (patch)
treeaa01c77f2709ee09e611c8fa683e7aa028566b15 /docs/ref
parent52a2588df69e5252bee98e76e8d3a2aa37bce23c (diff)
Fixed #19497 -- Refactored testing docs.
Thanks Tim Graham for the review and suggestions.
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/django-admin.txt6
-rw-r--r--docs/ref/settings.txt6
-rw-r--r--docs/ref/signals.txt2
3 files changed, 6 insertions, 8 deletions
diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt
index 306db8439e..6ab3b1d133 100644
--- a/docs/ref/django-admin.txt
+++ b/docs/ref/django-admin.txt
@@ -1036,7 +1036,7 @@ test <app or test identifier>
.. django-admin:: test
-Runs tests for all installed models. See :doc:`/topics/testing` for more
+Runs tests for all installed models. See :doc:`/topics/testing/index` for more
information.
.. django-admin-option:: --failfast
@@ -1072,7 +1072,7 @@ For example, this command::
...would perform the following steps:
-1. Create a test database, as described in :doc:`/topics/testing`.
+1. Create a test database, as described in :ref:`the-test-database`.
2. Populate the test database with fixture data from the given fixtures.
(For more on fixtures, see the documentation for ``loaddata`` above.)
3. Runs the Django development server (as in ``runserver``), pointed at
@@ -1080,7 +1080,7 @@ For example, this command::
This is useful in a number of ways:
-* When you're writing :doc:`unit tests </topics/testing>` of how your views
+* When you're writing :doc:`unit tests </topics/testing/overview>` of how your views
act with certain fixture data, you can use ``testserver`` to interact with
the views in a Web browser, manually.
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
index 135cddae25..5ecc221039 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -562,7 +562,7 @@ If the default value (``None``) is used with the SQLite database engine, the
tests will use a memory resident database. For all other database engines the
test database will use the name ``'test_' + DATABASE_NAME``.
-See :doc:`/topics/testing`.
+See :ref:`the-test-database`.
.. setting:: TEST_CREATE
@@ -1982,9 +1982,7 @@ TEST_RUNNER
Default: ``'django.test.simple.DjangoTestSuiteRunner'``
The name of the class to use for starting the test suite. See
-:doc:`/topics/testing`.
-
-.. _Testing Django Applications: ../testing/
+:ref:`other-testing-frameworks`.
.. setting:: THOUSAND_SEPARATOR
diff --git a/docs/ref/signals.txt b/docs/ref/signals.txt
index 0db540370d..3315f9781b 100644
--- a/docs/ref/signals.txt
+++ b/docs/ref/signals.txt
@@ -476,7 +476,7 @@ Test signals
.. module:: django.test.signals
:synopsis: Signals sent during testing.
-Signals only sent when :doc:`running tests </topics/testing>`.
+Signals only sent when :ref:`running tests <running-tests>`.
setting_changed
---------------