In earlier versions it was only possible to run individual test methods and

not modules or classes.

Test Discovery

unittest supports simple test discovery. For a project's tests to be

compatible with test discovery they must all be importable from the top level

If :meth:`setUp` fails, meaning that :meth:`tearDown` is not called,

then any cleanup functions added will still be called.

.. method:: doCleanups()

:meth:`doCleanups` pops methods off the stack of cleanup

functions one at a time, so it can be called at any time.

.. class:: FunctionTestCase(testFunc, setUp=None, tearDown=None, description=None)

(for example when counting tests or comparing for equality)

so the tests returned must be the same for repeated iterations.

In earlier versions the :class:`TestSuite` accessed tests directly rather

than through iteration, so overriding :meth:`__iter__` wasn't sufficient

for providing tests.

load the tests. This allows modules to customize test loading.

This is the `load_tests protocol`_.

Support for ``load_tests`` added.

``load_tests`` does not need to pass this argument in to

``loader.discover()``.

The following attributes of a :class:`TestLoader` can be configured either by

subclassing or assignment on an instance:

Called once before any tests are executed.

.. method:: stopTestRun(test)

Called once after all tests are executed.

.. method:: addError(test, err)

Calling ``main`` actually returns an instance of the ``TestProgram`` class.

This stores the result of the tests run as the ``result`` attribute.

The ``exit`` and ``verbosity`` parameters were added.

load_tests Protocol

Modules or packages can customize how tests are loaded from them during normal