[TIP] plguins for unittest2?

Chris Withers chris at simplistix.co.uk
Fri Oct 21 10:26:57 PDT 2011

On 16/10/2011 14:13, Alfredo Deza wrote:
> On Sun, Oct 16, 2011 at 4:55 AM, Robert Collins
> <robertc at robertcollins.net>  wrote:
>> On Sun, Oct 16, 2011 at 1:08 AM, meme dough<memedough at gmail.com>  wrote:
>>> Both py.test and nose (and presumably unit2) collect stdout / stderr
>>> and so hide it by default.  Why is this annoying?  You see the output
>>> if a test fails.
>> It interferes with debugging, both adhoc and pdb. Its unnecessary
>> complexity, and it -totally- fails in parallel test (via threads)
>> environments.
> That statement is confusing to me. How is it that capturing stdout and
> stderr an interference
> with debugging?

Try using pdb with stdout and stderr being captured ;-)

> If there is no failure why do you need to see
> stderr/stdout from a test run?

If there's no failure then you aren't debugging...

> And you are having issues with pdb? How so? all of the mentioned test
> runners have the ability to start a
> pdb on failure or stop at a given break point with the well known
> pdb.set_trace().

...try the latter in nose without disabling output capture ;-)


Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk

More information about the testing-in-python mailing list