[issue1207] Load tests from path (patch included)

Michael Foord added the comment: Similar functionality is now in TestLoader.discover. -- resolution: -> rejected status: open -> closed ___ Python tracker ___ __

[issue1207] Load tests from path (patch included)

Michael Foord added the comment: See issue 6001 for a patch implementing test discovery for unittest. It would allow you to do: python -m unittest discover -- ___ Python tracker __

[issue1207] Load tests from path (patch included)

Michael Foord added the comment: I'm intending to implement loadTestsFromPackage which will do a *similar* job. As well as allowing test autodiscovery it will allow for customizing test loading from modules / packages using a protocol thrashed out on the Testing in Python mailing list.

[issue1207] Load tests from path (patch included)

Changes by Daniel Diniz : -- nosy: +michael.foord stage: -> test needed versions: +Python 2.7, Python 3.1 -Python 2.5 ___ Python tracker ___ _

[issue1207] Load tests from path (patch included)

Sean Reifschneider <[EMAIL PROTECTED]> added the comment: Patch is inline. A few notes for submitter: This also needs to include a documentation patch before it can be accepted. Please format the docstring for a line length of 78 characters or less. Ideally, please submit a "diff -c" style pa

[issue1207] Load tests from path (patch included)

New submission from Bluebird: Something very nice about unittest is that it can find automatically the TestCase that you declare, and the test methods of every test case. This makes the operation of adding or removing tests very simple. For test modules however, there is nothing to automatically