mirror of
https://github.com/django/django.git
synced 2024-12-23 09:36:06 +00:00
Fixed some ReST errors in docs/testing.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@5891 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
3bfda4fa62
commit
4f62b0a193
@ -213,7 +213,7 @@ For developers new to testing, however, this choice can seem confusing. Here,
|
|||||||
then, are a few key differences to help you decide which approach is right for
|
then, are a few key differences to help you decide which approach is right for
|
||||||
you:
|
you:
|
||||||
|
|
||||||
* If you've been using Python for a while, ``doctest`` will probably feel
|
* If you've been using Python for a while, ``doctest`` will probably feel
|
||||||
more "pythonic". It's designed to make writing tests as easy as possible,
|
more "pythonic". It's designed to make writing tests as easy as possible,
|
||||||
so it requires no overhead of writing classes or methods. You simply put
|
so it requires no overhead of writing classes or methods. You simply put
|
||||||
tests in docstrings. This has the added advantage of serving as
|
tests in docstrings. This has the added advantage of serving as
|
||||||
@ -561,7 +561,7 @@ The ``get()`` and ``post()`` methods both return a ``Response`` object. This
|
|||||||
Django views; this object is simpler and has some additional data useful for
|
Django views; this object is simpler and has some additional data useful for
|
||||||
tests.
|
tests.
|
||||||
|
|
||||||
Specifically, a ``Response`` object has the following attributes::
|
Specifically, a ``Response`` object has the following attributes:
|
||||||
|
|
||||||
=============== ==========================================================
|
=============== ==========================================================
|
||||||
Attribute Description
|
Attribute Description
|
||||||
|
Loading…
Reference in New Issue
Block a user