[TIP] Result protocol / problems being solved

Olemis Lang olemis at gmail.com
Tue Apr 14 06:25:34 PDT 2009

On Mon, Apr 13, 2009 at 9:43 PM, Douglas Philips <dgou at mac.com> wrote:
> On 2009 Apr 13, at 10:18 PM, laidler at stsci.edu wrote:
>> I'm going to take a step yet further back and ask, what are the
>> problems people are trying to solve here?
> Yay!

Nice move ;)

>> 7. I want to be able to figure out why this specific test failed.
>> Implications: Allow a way to associate stdout/stderr with the test
>> result.
> Those are two things I want, yes, but I also want the ability to
> attach other output stream (trace logs for different trace flags, for
> example).

Perhaps this can be solved with the proposal I made in a separate
thread about including test status objects in TestResult.(failures |
errors | +successful ) People could be able to include anything they
want inside such objects (BTW anything you can imagine ;)

>> Did I miss anything?
> I agree with everything you've said, and would emphasize just this:
> SIMPLICITY of result reporting... only report what you have. No empty
> place holders.


> Thanks for the excellent summary, wish I'd've thought of it!




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