Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit d21fd7b

Browse files
committed
* Minor wording change
* Reference the doctest.DocTestSuite() conversion tool.
1 parent 3404034 commit d21fd7b

1 file changed

Lines changed: 8 additions & 2 deletions

File tree

Doc/lib/libunittest.tex

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ \section{\module{unittest} ---
9191
\end{seealso}
9292

9393

94-
\subsection{Minimal example \label{minimal-example}}
94+
\subsection{Basic example \label{minimal-example}}
9595

9696
The \module{unittest} module provides a rich set of tools for
9797
constructing and running tests. This section demonstrates that a
@@ -387,7 +387,7 @@ \subsection{Organizing test code
387387
\end{verbatim}
388388

389389
You can place the definitions of test cases and test suites in the
390-
same modules as the code they are to test (e.g.\ \file{widget.py}),
390+
same modules as the code they are to test (such as \file{widget.py}),
391391
but there are several advantages to placing the test code in a
392392
separate module, such as \file{widgettests.py}:
393393

@@ -516,6 +516,12 @@ \subsection{Classes and functions
516516
\end{verbatim}
517517
\end{funcdesc}
518518

519+
In some cases, the existing tests may have be written using the
520+
\module{doctest} module. If so, that module provides a
521+
\class{DocTestSuite} class that can automatically build
522+
\class{unittest.TestSuite} instances from the existing test code.
523+
\versionadded{2.3}
524+
519525

520526
\subsection{TestCase Objects
521527
\label{testcase-objects}}

0 commit comments

Comments
 (0)