Lines Matching refs:discovery

72    a GUI tool for test discovery and execution.  This is intended largely for ease of use
184 When executed without arguments :ref:`unittest-test-discovery` is started::
232 The command line can also be used for test discovery, for running all of the
236 .. _unittest-test-discovery:
243 Unittest supports simple test discovery. In order to be compatible with test
244 discovery, all of the test files must be :ref:`modules <tut-modules>` or
250 Test discovery is implemented in :meth:`TestLoader.discover`, but can also be
260    discovery the ``discover`` sub-command must be used explicitly.
272    Directory to start discovery (``.`` default)
296     Test discovery loads tests by importing them. Once test discovery has found
301     If you have a package installed globally and attempt test discovery on
303     wrong place. If this happens test discovery will warn you and exit.
310 Test modules and packages can customize test loading and discovery by through
314    Test discovery supports :term:`namespace packages <namespace package>`.
1673       this will be recorded as a single error and discovery will continue.  If
1680       ``package.load_tests(loader, tests, pattern)``. Test discovery takes care
1685       If ``load_tests`` exists then discovery does *not* recurse into the
1690       packages can continue discovery themselves. *top_level_dir* is stored so
2082 test runs or test discovery by implementing a function called ``load_tests``.
2098 The third argument is used when loading packages as part of test discovery.
2112 If discovery is started in a directory containing a package, either from the
2115 not exist, discovery will recurse into the package as though it were just
2116 another directory.  Otherwise, discovery of the package's tests will be left up
2126 continue (and potentially modify) test discovery. A 'do nothing'