MOON
Server: Apache/2.2.31 (Unix) mod_ssl/2.2.31 OpenSSL/0.9.8e-fips-rhel5 mod_bwlimited/1.4
System: Linux csr818.wilogic.com 2.6.18-419.el5xen #1 SMP Fri Feb 24 22:50:37 UTC 2017 x86_64
User: digitals (531)
PHP: 5.4.45
Disabled: NONE
Upload Files
File: //usr/local/ssl/local/ssl/share/doc/python-docs-2.4.3/html/lib/doctest-basic-api.html
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<link rel="STYLESHEET" href="lib.css" type='text/css' />
<link rel="SHORTCUT ICON" href="../icons/pyfav.png" type="image/png" />
<link rel='start' href='../index.html' title='Python Documentation Index' />
<link rel="first" href="lib.html" title='Python Library Reference' />
<link rel='contents' href='contents.html' title="Contents" />
<link rel='index' href='genindex.html' title='Index' />
<link rel='last' href='about.html' title='About this document...' />
<link rel='help' href='about.html' title='About this document...' />
<link rel="next" href="doctest-unittest-api.html" />
<link rel="prev" href="doctest-how-it-works.html" />
<link rel="parent" href="module-doctest.html" />
<link rel="next" href="doctest-unittest-api.html" />
<meta name='aesop' content='information' />
<title>5.2.4 Basic API</title>
</head>
<body>
<DIV CLASS="navigation">
<div id='top-navigation-panel' xml:id='top-navigation-panel'>
<table align="center" width="100%" cellpadding="0" cellspacing="2">
<tr>
<td class='online-navigation'><a rel="prev" title="5.2.3.6 Warnings"
  href="doctest-warnings.html"><img src='../icons/previous.png'
  border='0' height='32'  alt='Previous Page' width='32' /></A></td>
<td class='online-navigation'><a rel="parent" title="5.2 doctest  "
  href="module-doctest.html"><img src='../icons/up.png'
  border='0' height='32'  alt='Up One Level' width='32' /></A></td>
<td class='online-navigation'><a rel="next" title="5.2.5 Unittest API"
  href="doctest-unittest-api.html"><img src='../icons/next.png'
  border='0' height='32'  alt='Next Page' width='32' /></A></td>
<td align="center" width="100%">Python Library Reference</td>
<td class='online-navigation'><a rel="contents" title="Table of Contents"
  href="contents.html"><img src='../icons/contents.png'
  border='0' height='32'  alt='Contents' width='32' /></A></td>
<td class='online-navigation'><a href="modindex.html" title="Module Index"><img src='../icons/modules.png'
  border='0' height='32'  alt='Module Index' width='32' /></a></td>
<td class='online-navigation'><a rel="index" title="Index"
  href="genindex.html"><img src='../icons/index.png'
  border='0' height='32'  alt='Index' width='32' /></A></td>
</tr></table>
<div class='online-navigation'>
<b class="navlabel">Previous:</b>
<a class="sectref" rel="prev" href="doctest-warnings.html">5.2.3.6 Warnings</A>
<b class="navlabel">Up:</b>
<a class="sectref" rel="parent" href="module-doctest.html">5.2 doctest  </A>
<b class="navlabel">Next:</b>
<a class="sectref" rel="next" href="doctest-unittest-api.html">5.2.5 Unittest API</A>
</div>
<hr /></div>
</DIV>
<!--End of Navigation Panel-->

<H2><A NAME="SECTION007240000000000000000"></A><A NAME="doctest-basic-api"></A>
<BR>
5.2.4 Basic API
</H2>

<P>
The functions <tt class="function">testmod()</tt> and <tt class="function">testfile()</tt> provide a
simple interface to doctest that should be sufficient for most basic
uses.  For a less formal introduction to these two functions, see
sections <A href="doctest-simple-testmod.html#doctest-simple-testmod">5.2.1</A> and
<A href="doctest-simple-testfile.html#doctest-simple-testfile">5.2.2</A>.

<P>
<dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
  <td><nobr><b><tt id='l2h-1074' xml:id='l2h-1074' class="function">testfile</tt></b>(</nobr></td>
  <td><var>filename</var><big>[</big><var>, module_relative</var><big>]</big><var></var><big>[</big><var>,
                          name</var><big>]</big><var></var><big>[</big><var>, package</var><big>]</big><var></var><big>[</big><var>,
                          globs</var><big>]</big><var></var><big>[</big><var>, verbose</var><big>]</big><var></var><big>[</big><var>,
                          report</var><big>]</big><var></var><big>[</big><var>, optionflags</var><big>]</big><var></var><big>[</big><var>,
                          extraglobs</var><big>]</big><var></var><big>[</big><var>, raise_on_error</var><big>]</big><var></var><big>[</big><var>,
                          parser</var><big>]</big><var></var>)</td></tr></table></dt>
<dd>

<P>
All arguments except <var>filename</var> are optional, and should be
  specified in keyword form.

<P>
Test examples in the file named <var>filename</var>.  Return
  "<tt class="samp">(<var>failure_count</var>, <var>test_count</var>)</tt>".

<P>
Optional argument <var>module_relative</var> specifies how the filename
  should be interpreted:

<P>

<UL>
<LI>If <var>module_relative</var> is <code>True</code> (the default), then
        <var>filename</var> specifies an OS-independent module-relative
        path.  By default, this path is relative to the calling
        module's directory; but if the <var>package</var> argument is
        specified, then it is relative to that package.  To ensure
        OS-independence, <var>filename</var> should use <code>/</code> characters
        to separate path segments, and may not be an absolute path
        (i.e., it may not begin with <code>/</code>).
</LI>
<LI>If <var>module_relative</var> is <code>False</code>, then <var>filename</var>
        specifies an OS-specific path.  The path may be absolute or
        relative; relative paths are resolved with respect to the
        current working directory.
  
</LI>
</UL>

<P>
Optional argument <var>name</var> gives the name of the test; by default,
  or if <code>None</code>, <code>os.path.basename(<var>filename</var>)</code> is used.

<P>
Optional argument <var>package</var> is a Python package or the name of a
  Python package whose directory should be used as the base directory
  for a module-relative filename.  If no package is specified, then
  the calling module's directory is used as the base directory for
  module-relative filenames.  It is an error to specify <var>package</var>
  if <var>module_relative</var> is <code>False</code>.

<P>
Optional argument <var>globs</var> gives a dict to be used as the globals
  when executing examples.  A new shallow copy of this dict is
  created for the doctest, so its examples start with a clean slate.
  By default, or if <code>None</code>, a new empty dict is used.

<P>
Optional argument <var>extraglobs</var> gives a dict merged into the
  globals used to execute examples.  This works like
  <tt class="method">dict.update()</tt>:  if <var>globs</var> and <var>extraglobs</var> have a
  common key, the associated value in <var>extraglobs</var> appears in the
  combined dict.  By default, or if <code>None</code>, no extra globals are
  used.  This is an advanced feature that allows parameterization of
  doctests.  For example, a doctest can be written for a base class, using
  a generic name for the class, then reused to test any number of
  subclasses by passing an <var>extraglobs</var> dict mapping the generic
  name to the subclass to be tested.

<P>
Optional argument <var>verbose</var> prints lots of stuff if true, and prints
  only failures if false; by default, or if <code>None</code>, it's true
  if and only if <code>'-v'</code> is in <code>sys.argv</code>.

<P>
Optional argument <var>report</var> prints a summary at the end when true,
  else prints nothing at the end.  In verbose mode, the summary is
  detailed, else the summary is very brief (in fact, empty if all tests
  passed).

<P>
Optional argument <var>optionflags</var> or's together option flags.  See
  section&nbsp;<A href="doctest-options.html#doctest-options">5.2.3</A>.

<P>
Optional argument <var>raise_on_error</var> defaults to false.  If true,
  an exception is raised upon the first failure or unexpected exception
  in an example.  This allows failures to be post-mortem debugged.
  Default behavior is to continue running examples.

<P>
Optional argument <var>parser</var> specifies a <tt class="class">DocTestParser</tt> (or
  subclass) that should be used to extract tests from the files.  It
  defaults to a normal parser (i.e., <code><tt class="class">DocTestParser</tt>()</code>).

<P>

<span class="versionnote">New in version 2.4.</span>

</dl>

<P>
<dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
  <td><nobr><b><tt id='l2h-1075' xml:id='l2h-1075' class="function">testmod</tt></b>(</nobr></td>
  <td><var></var><big>[</big><var>m</var><big>]</big><var></var><big>[</big><var>, name</var><big>]</big><var></var><big>[</big><var>,
                          globs</var><big>]</big><var></var><big>[</big><var>, verbose</var><big>]</big><var></var><big>[</big><var>,
                          isprivate</var><big>]</big><var></var><big>[</big><var>, report</var><big>]</big><var></var><big>[</big><var>,
                          optionflags</var><big>]</big><var></var><big>[</big><var>, extraglobs</var><big>]</big><var></var><big>[</big><var>,
                          raise_on_error</var><big>]</big><var></var><big>[</big><var>, exclude_empty</var><big>]</big><var></var>)</td></tr></table></dt>
<dd>

<P>
All arguments are optional, and all except for <var>m</var> should be
  specified in keyword form.

<P>
Test examples in docstrings in functions and classes reachable
  from module <var>m</var> (or module <tt class="module">__main__</tt> if <var>m</var> is not
  supplied or is <code>None</code>), starting with <code><var>m</var>.__doc__</code>.

<P>
Also test examples reachable from dict <code><var>m</var>.__test__</code>, if it
  exists and is not <code>None</code>.  <code><var>m</var>.__test__</code> maps
  names (strings) to functions, classes and strings; function and class
  docstrings are searched for examples; strings are searched directly,
  as if they were docstrings.

<P>
Only docstrings attached to objects belonging to module <var>m</var> are
  searched.

<P>
Return "<tt class="samp">(<var>failure_count</var>, <var>test_count</var>)</tt>".

<P>
Optional argument <var>name</var> gives the name of the module; by default,
  or if <code>None</code>, <code><var>m</var>.__name__</code> is used.

<P>
Optional argument <var>exclude_empty</var> defaults to false.  If true,
  objects for which no doctests are found are excluded from consideration.
  The default is a backward compatibility hack, so that code still
  using <tt class="method">doctest.master.summarize()</tt> in conjunction with
  <tt class="function">testmod()</tt> continues to get output for objects with no tests.
  The <var>exclude_empty</var> argument to the newer <tt class="class">DocTestFinder</tt>
  constructor defaults to true.

<P>
Optional arguments <var>extraglobs</var>, <var>verbose</var>, <var>report</var>,
  <var>optionflags</var>, <var>raise_on_error</var>, and <var>globs</var> are the same as
  for function <tt class="function">testfile()</tt> above, except that <var>globs</var>
  defaults to <code><var>m</var>.__dict__</code>.

<P>
Optional argument <var>isprivate</var> specifies a function used to
  determine whether a name is private.  The default function treats
  all names as public.  <var>isprivate</var> can be set to
  <code>doctest.is_private</code> to skip over names that are
  private according to Python's underscore naming convention.
  <div class="versionnote"><b>Deprecated since release 2.4.</b>
<var>isprivate</var> was a stupid idea - don't use it.
  If you need to skip tests based on name, filter the list returned by
  <code>DocTestFinder.find()</code> instead.</div><p></p>

<P>

<span class="versionnote">Changed in version 2.3:
The parameter <var>optionflags</var> was added.</span>

<P>

<span class="versionnote">Changed in version 2.4:
The parameters <var>extraglobs</var>, <var>raise_on_error</var>
                  and <var>exclude_empty</var> were added.</span>

</dl>

<P>
There's also a function to run the doctests associated with a single object.
This function is provided for backward compatibility.  There are no plans
to deprecate it, but it's rarely useful:

<P>
<dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
  <td><nobr><b><tt id='l2h-1076' xml:id='l2h-1076' class="function">run_docstring_examples</tt></b>(</nobr></td>
  <td><var>f, globs</var><big>[</big><var>,
                            verbose</var><big>]</big><var></var><big>[</big><var>, name</var><big>]</big><var></var><big>[</big><var>,
                            compileflags</var><big>]</big><var></var><big>[</big><var>, optionflags</var><big>]</big><var></var>)</td></tr></table></dt>
<dd>

<P>
Test examples associated with object <var>f</var>; for example, <var>f</var> may
  be a module, function, or class object.

<P>
A shallow copy of dictionary argument <var>globs</var> is used for the
  execution context.

<P>
Optional argument <var>name</var> is used in failure messages, and defaults
  to <code>"NoName"</code>.

<P>
If optional argument <var>verbose</var> is true, output is generated even
  if there are no failures.  By default, output is generated only in case
  of an example failure.

<P>
Optional argument <var>compileflags</var> gives the set of flags that should
  be used by the Python compiler when running the examples.  By default, or
  if <code>None</code>, flags are deduced corresponding to the set of future
  features found in <var>globs</var>.

<P>
Optional argument <var>optionflags</var> works as for function
  <tt class="function">testfile()</tt> above.
</dl>

<P>

<DIV CLASS="navigation">
<div class='online-navigation'>
<p></p><hr />
<table align="center" width="100%" cellpadding="0" cellspacing="2">
<tr>
<td class='online-navigation'><a rel="prev" title="5.2.3.6 Warnings"
  href="doctest-warnings.html"><img src='../icons/previous.png'
  border='0' height='32'  alt='Previous Page' width='32' /></A></td>
<td class='online-navigation'><a rel="parent" title="5.2 doctest  "
  href="module-doctest.html"><img src='../icons/up.png'
  border='0' height='32'  alt='Up One Level' width='32' /></A></td>
<td class='online-navigation'><a rel="next" title="5.2.5 Unittest API"
  href="doctest-unittest-api.html"><img src='../icons/next.png'
  border='0' height='32'  alt='Next Page' width='32' /></A></td>
<td align="center" width="100%">Python Library Reference</td>
<td class='online-navigation'><a rel="contents" title="Table of Contents"
  href="contents.html"><img src='../icons/contents.png'
  border='0' height='32'  alt='Contents' width='32' /></A></td>
<td class='online-navigation'><a href="modindex.html" title="Module Index"><img src='../icons/modules.png'
  border='0' height='32'  alt='Module Index' width='32' /></a></td>
<td class='online-navigation'><a rel="index" title="Index"
  href="genindex.html"><img src='../icons/index.png'
  border='0' height='32'  alt='Index' width='32' /></A></td>
</tr></table>
<div class='online-navigation'>
<b class="navlabel">Previous:</b>
<a class="sectref" rel="prev" href="doctest-warnings.html">5.2.3.6 Warnings</A>
<b class="navlabel">Up:</b>
<a class="sectref" rel="parent" href="module-doctest.html">5.2 doctest  </A>
<b class="navlabel">Next:</b>
<a class="sectref" rel="next" href="doctest-unittest-api.html">5.2.5 Unittest API</A>
</div>
</div>
<hr />
<span class="release-info">Release 2.4.3, documentation updated on 29 March 2006.</span>
</DIV>
<!--End of Navigation Panel-->
<ADDRESS>
See <i><a href="about.html">About this document...</a></i> for information on suggesting changes.
</ADDRESS>
</BODY>
</HTML>