traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Convert PyUnit -> unittest. Backported from r54929.

This commit is contained in:
Collin Winter 2007-04-24 03:52:08 +00:00
parent 2f131d81e2
commit 6def78ae85
1 changed files with 10 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
Lib/test/README
View File

@ -15,7 +15,7 @@ testing facility provided with Python; any particular test should use only
one of these options. Each option requires writing a test module using the one of these options. Each option requires writing a test module using the
conventions of the selected option: conventions of the selected option:
- PyUnit_ based tests - unittest_ based tests
- doctest_ based tests - doctest_ based tests
- "traditional" Python test modules - "traditional" Python test modules
@ -28,27 +28,26 @@ your test cases to exercise it more completely. In particular, you will be
able to refer to the C and Python code in the CVS repository when writing able to refer to the C and Python code in the CVS repository when writing
your regression test cases. your regression test cases.
.. _PyUnit:
.. _unittest: http://www.python.org/doc/current/lib/module-unittest.html .. _unittest: http://www.python.org/doc/current/lib/module-unittest.html
.. _doctest: http://www.python.org/doc/current/lib/module-doctest.html .. _doctest: http://www.python.org/doc/current/lib/module-doctest.html
PyUnit based tests unittest-based tests
------------------ ------------------
The PyUnit_ framework is based on the ideas of unit testing as espoused The unittest_ framework is based on the ideas of unit testing as espoused
by Kent Beck and the `Extreme Programming`_ (XP) movement. The specific by Kent Beck and the `Extreme Programming`_ (XP) movement. The specific
interface provided by the framework is tightly based on the JUnit_ interface provided by the framework is tightly based on the JUnit_
Java implementation of Beck's original SmallTalk test framework. Please Java implementation of Beck's original SmallTalk test framework. Please
see the documentation of the unittest_ module for detailed information on see the documentation of the unittest_ module for detailed information on
the interface and general guidelines on writing PyUnit based tests. the interface and general guidelines on writing unittest-based tests.
The test_support helper module provides two functions for use by The test_support helper module provides two functions for use by
PyUnit based tests in the Python regression testing framework: unittest-based tests in the Python regression testing framework:
- ``run_unittest()`` takes a ``unittest.TestCase`` derived class as a - ``run_unittest()`` takes a number of ``unittest.TestCase`` derived class as
parameter and runs the tests defined in that class parameters and runs the tests defined in those classes.
- ``run_suite()`` takes a populated ``TestSuite`` instance and runs the - ``run_suite()`` takes a populated ``TestSuite`` instance and runs the
tests tests.
``run_suite()`` is preferred because unittest files typically grow multiple ``run_suite()`` is preferred because unittest files typically grow multiple
test classes, and you might as well be prepared. test classes, and you might as well be prepared.
@ -63,7 +62,7 @@ and the full class name. When there's a problem with a test, the
latter information makes it easier to find the source for the test latter information makes it easier to find the source for the test
than the docstring. than the docstring.
All PyUnit-based tests in the Python test suite use boilerplate that All unittest-based tests in the Python test suite use boilerplate that
looks like this (with minor variations):: looks like this (with minor variations)::
import unittest import unittest
@ -415,7 +414,7 @@ Some Non-Obvious regrtest Features
This is rarely required with the "traditional" Python tests, and This is rarely required with the "traditional" Python tests, and
you shouldn't create a module global with name test_main unless you shouldn't create a module global with name test_main unless
you're specifically exploiting this gimmick. This usage does you're specifically exploiting this gimmick. This usage does
prove useful with PyUnit-based tests as well, however; defining prove useful with unittest-based tests as well, however; defining
a ``test_main()`` which is run by regrtest and a script-stub in the a ``test_main()`` which is run by regrtest and a script-stub in the
test module ("``if __name__ == '__main__': test_main()``") allows test module ("``if __name__ == '__main__': test_main()``") allows
the test to be used like any other Python test and also work the test to be used like any other Python test and also work