diff options
| author | Boulder Sprinters <boulder-sprinters@djangoproject.com> | 2007-05-31 16:09:49 +0000 |
|---|---|---|
| committer | Boulder Sprinters <boulder-sprinters@djangoproject.com> | 2007-05-31 16:09:49 +0000 |
| commit | a62ee775ef53a8e98911dc0e42587753f541d254 (patch) | |
| tree | af7d09e8a6367f41e5960c697f7ab97b6a774249 /docs | |
| parent | a82d071b484b6a3b429f5ed1c635a6f0e46f9636 (diff) | |
boulder-oracle-sprint: Merged to [5392]
git-svn-id: http://code.djangoproject.com/svn/django/branches/boulder-oracle-sprint@5393 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -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. |