[Python-checkins] python/dist/src/Doc/lib libtest.tex,1.1,1.2

2003年5月09日 12:10:15 -0700

Update of /cvsroot/python/python/dist/src/Doc/lib
In directory sc8-pr-cvs1:/tmp/cvs-serv21428
Modified Files:
	libtest.tex 
Log Message:
Make this format again.
Index: libtest.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/lib/libtest.tex,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** libtest.tex	7 May 2003 22:02:17 -0000	1.1
--- libtest.tex	9 May 2003 19:10:12 -0000	1.2
***************
*** 30,40 ****

! \subsection{test_support \label{test_support-docs}}
! 
! The \module{test_support} module contains functions for assisting with writing
! regression tests.

! The \module{test_support} module defines the following exceptions:

 \begin{excdesc}{TestFailed}
--- 30,41 ----

! \subsection{\module[test.testsupport]{test.test_support} ---
! --- Utility functions for tests}
! \declaremodule[test.testsupport]{standard}{test.test_support}

+ The \module{test.test_support} module contains functions for assisting
+ with writing regression tests.

! The \module{test.test_support} module defines the following exceptions:

 \begin{excdesc}{TestFailed}
***************
*** 90,94 ****
 The list of available resources is only set when \module{regrtest.py} is
 executing the tests.
! \end{funcdest}

 \begin{funcdesc}{requires}{resource\optional{, msg}}
--- 91,95 ----
 The list of available resources is only set when \module{regrtest.py} is
 executing the tests.
! \end{funcdesc}

 \begin{funcdesc}{requires}{resource\optional{, msg}}
***************
*** 111,115 ****
 \code{"test_"} and executes the tests individually.
 This is the preferred way to execute tests.
! \end{datadesc}

 \begin{funcdesc}{run_suite}{suite\optional{, testclass=None}}
--- 112,116 ----
 \code{"test_"} and executes the tests individually.
 This is the preferred way to execute tests.
! \end{funcdesc}

 \begin{funcdesc}{run_suite}{suite\optional{, testclass=None}}
***************
*** 122,129 ****

! \subsection{Writing Unit Tests for the \module{test} package \label{writing-tests}}

 It is preferred that tests for the \module{test} package use the
! \module{unittest} module and follow a few guidelines.
 One is to have the name of all the test methods start with \code{"test_"} as
 well as the module's name.
--- 123,131 ----

! \subsection{Writing Unit Tests for the \module{test} package%
! \label{writing-tests}}

 It is preferred that tests for the \module{test} package use the
! \refmodule{unittest} module and follow a few guidelines.
 One is to have the name of all the test methods start with \code{"test_"} as
 well as the module's name.
***************
*** 132,136 ****
 Also, no documentation string for the method should be included.
 A comment (such as
! \var{# Tests function returns only True or False}) should be used to provide
 documentation for test methods.
 This is done because documentation strings get printed out if they exist and
--- 134,138 ----
 Also, no documentation string for the method should be included.
 A comment (such as
! \code{\# Tests function returns only True or False}) should be used to provide
 documentation for test methods.
 This is done because documentation strings get printed out if they exist and