[TIP] Guidelines for where to put tests & how to package them

Olemis Lang olemis at gmail.com
Fri Feb 26 12:49:37 PST 2010

On Fri, Feb 26, 2010 at 3:41 PM, Robert Collins
<robertc at robertcollins.net> wrote:
> On Fri, 2010-02-26 at 18:29 +0000, Michael Foord wrote:
>> The advantage of having a run module that collects and runs the tests
>> is that it is agnostic of which test runner is used (or at least
>> allows the *user* to be agnostic, so long as they have the right
>> dependencies installed anyway).
> Except they need to know command line options to get JUnit xml out (or
> whatever the particular CI tool needs).
> The point of the load_tests hook + discover is that with them you have
> complete control over collection, regardless of test executor being
> chosen: as long as the test executor obeys the protocol.


That's the flexibility I cannot see when using `run script` (you'll
end up reinventing distutils to get similar behavior ;o)



Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

More information about the testing-in-python mailing list