Issue #22153: Improve unittest docs. Patch from Martin Panter and evilzero.

This commit is contained in:
Robert Collins 2015-07-23 06:37:26 +12:00
parent 689b55c1cb
commit e02f6c20ff
3 changed files with 11 additions and 4 deletions

View File

@ -644,10 +644,8 @@ Test cases
kinds of failure.
Each instance of :class:`TestCase` will run a single base method: the method
named *methodName*. However, the standard implementation of the default
*methodName*, ``runTest()``, will run every method starting with ``test``
as an individual test, and count successes and failures accordingly.
Therefore, in most uses of :class:`TestCase`, you will neither change
named *methodName*.
In most uses of :class:`TestCase`, you will neither change
the *methodName* nor reimplement the default ``runTest()`` method.
.. versionchanged:: 3.2
@ -1551,6 +1549,12 @@ Loading and running tests
Return a suite of all tests cases contained in the :class:`TestCase`\ -derived
:class:`testCaseClass`.
A test case instance is created for each method named by
:meth:`getTestCaseNames`. By default these are the method names
beginning with ``test``. If :meth:`getTestCaseNames` returns no
methods, but the :meth:`runTest` method is implemented, a single test
case is created for that method instead.
.. method:: loadTestsFromModule(module)

View File

@ -1535,3 +1535,4 @@ Doug Zongker
Peter Åstrand
Laurent De Buyst
Nicola Palumbo
evilzero

View File

@ -66,6 +66,8 @@ Core and Builtins
Library
-------
- Issue #22153: Improve unittest docs. Patch from Martin Panter and evilzero.
- Issue #24206: Fixed __eq__ and __ne__ methods of inspect classes.
- Issue #21750: mock_open.read_data can now be read from each instance, as it