From a62ee775ef53a8e98911dc0e42587753f541d254 Mon Sep 17 00:00:00 2001 From: Boulder Sprinters Date: Thu, 31 May 2007 16:09:49 +0000 Subject: 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 --- docs/testing.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs') 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. -- cgit v1.3