mirror of
https://github.com/django/django.git
synced 2025-08-04 19:08:28 +00:00
Fixed #19497 -- Refactored testing docs.
Thanks Tim Graham for the review and suggestions.
This commit is contained in:
parent
52a2588df6
commit
d19109fd37
21 changed files with 849 additions and 801 deletions
|
@ -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.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue