diff options
| author | Adrian Holovaty <adrian@holovaty.com> | 2007-05-31 04:30:40 +0000 |
|---|---|---|
| committer | Adrian Holovaty <adrian@holovaty.com> | 2007-05-31 04:30:40 +0000 |
| commit | 8d3026bd9412a85f9e915aadf27745b0ec317e6e (patch) | |
| tree | 10370a58a614da3147bbe553d8e8c63355715e8a /docs/testing.txt | |
| parent | bf2e62aa3c1244c46cc99b255c8e4186a278da28 (diff) | |
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
Diffstat (limited to 'docs/testing.txt')
| -rw-r--r-- | docs/testing.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/testing.txt b/docs/testing.txt index 4a6d5694f5..dedb1e15a8 100644 --- a/docs/testing.txt +++ b/docs/testing.txt @@ -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 "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 -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 testing bird with a single stone. |