[TIP] RFC: additional data in unittest TestResult outcomes
olemis at gmail.com
Mon Sep 28 06:08:42 PDT 2009
On Tue, Sep 22, 2009 at 7:37 AM, Robert Collins
<robertc at robertcollins.net> wrote:
> On Tue, 2009-09-22 at 12:59 +0100, Michael Foord wrote:
>> Robert Collins wrote:
>> > On Tue, 2009-09-22 at 12:42 +0100, Michael Foord wrote:
>> > I want to overhaul how we do outcomes too; we have too many methods and
>> > its unclear what things like:
>> > result.startTest(self)
>> > result.addSuccess(self)
>> > result.addSkipped(self, "haha")
>> > result.stopTest(self)
>> > mean.
>> Really? They seem pretty clear to me.
to me too ...
> Imagine that you saw that sequence of calls in a trace :)
... but in this case I infer that the only thing that happened is that
a custom testing framework has been used and that such framework
didn't pay attention to Harry Potter's flippendo . IOW, they didn't
# Hide this module from tracebacks written into test results.
__unittessts = True
That's why such methods are shown in tracebacks included in test
results . CMIIW anyway, perhaps I didn't understand what u were
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Sobrepasa las 300 descargas el módulo dutest -
More information about the testing-in-python