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::
251 The command line can also be used for test discovery, for running all of the
255 .. _unittest-test-discovery:
262 Unittest supports simple test discovery. In order to be compatible with test
263 discovery, all of the test files must be :ref:`modules <tut-modules>` or
269 Test discovery is implemented in :meth:`TestLoader.discover`, but can also be
279    discovery the ``discover`` sub-command must be used explicitly.
291    Directory to start discovery (``.`` default)
315     Test discovery loads tests by importing them. Once test discovery has found
320     If you have a package installed globally and attempt test discovery on
322     wrong place. If this happens test discovery will warn you and exit.
329 Test modules and packages can customize test loading and discovery by through
333    Test discovery supports :term:`namespace packages <namespace package>`
1850       this will be recorded as a single error and discovery will continue.  If
1857       ``package.load_tests(loader, tests, pattern)``. Test discovery takes care
1862       If ``load_tests`` exists then discovery does *not* recurse into the
1867       packages can continue discovery themselves. *top_level_dir* is stored so
2278 test runs or test discovery by implementing a function called ``load_tests``.
2294 The third argument is used when loading packages as part of test discovery.
2308 If discovery is started in a directory containing a package, either from the
2311 not exist, discovery will recurse into the package as though it were just
2312 another directory.  Otherwise, discovery of the package's tests will be left up
2322 continue (and potentially modify) test discovery. A 'do nothing'