Fixed #4439 -- Fixed typo in docs/testing.txt. Thanks, hayley

git-svn-id: http://code.djangoproject.com/svn/django/trunk@5387 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2007-05-31 04:30:40 +00:00
parent bf2e62aa3c
commit 8d3026bd94
1 changed files with 1 additions and 1 deletions

View File

@ -147,7 +147,7 @@ doctests or unit tests are right for you.
If you've been using Python for a while, ``doctest`` will probably feel more 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, so "pythonic". It's designed to make writing tests as easy as possible, so
there's no overhead of writing classes or methods; you simply put tests in there's no overhead of writing classes or methods; you simply put tests in
docstrings. This gives the added advantage of given your modules automatic docstrings. This gives the added advantage of giving your modules automatic
documentation -- well-written doctests can kill both the documentation and the documentation -- well-written doctests can kill both the documentation and the
testing bird with a single stone. testing bird with a single stone.