[Python-checkins] python/dist/src/Doc/lib libunittest.tex, 1.14, 1.15

[rhettinger at users.sourceforge.net]

Update of /cvsroot/python/python/dist/src/Doc/lib
In directory sc8-pr-cvs1:/tmp/cvs-serv6908

Modified Files:
	libunittest.tex 
Log Message:
* Minor wording change
* Reference the doctest.DocTestSuite() conversion tool.



Index: libunittest.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libunittest.tex,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** libunittest.tex	10 Jul 2003 22:14:41 -0000	1.14
--- libunittest.tex	16 Sep 2003 22:04:31 -0000	1.15
***************
*** 92,96 ****
  
  
! \subsection{Minimal example \label{minimal-example}}
  
  The \module{unittest} module provides a rich set of tools for
--- 92,96 ----
  
  
! \subsection{Basic example \label{minimal-example}}
  
  The \module{unittest} module provides a rich set of tools for
***************
*** 388,392 ****
  
  You can place the definitions of test cases and test suites in the
! same modules as the code they are to test (e.g.\ \file{widget.py}),
  but there are several advantages to placing the test code in a
  separate module, such as \file{widgettests.py}:
--- 388,392 ----
  
  You can place the definitions of test cases and test suites in the
! same modules as the code they are to test (such as \file{widget.py}),
  but there are several advantages to placing the test code in a
  separate module, such as \file{widgettests.py}:
***************
*** 516,519 ****
--- 516,525 ----
  \end{verbatim}
  \end{funcdesc}
+ 
+ In some cases, the existing tests may have be written using the
+ \module{doctest} module.  If so, that module provides a 
+ \class{DocTestSuite} class that can automatically build
+ \class{unittest.TestSuite} instances from the existing test code.
+ \versionadded{2.3}