[TIP] RFC: additional data in unittest TestResult outcomes
robertc at robertcollins.net
Tue Sep 22 05:37:42 PDT 2009
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 have a preference for adding a keyword argument over proliferating
> >> methods. That's about my only comment at this point. :-)
> > 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.
Imagine that you saw that sequence of calls in a trace :) [I wasn't
listing the interface, but showing one of the extremely odd things I've
> > This stuff is what 'unittest ain't broke, lets fix it' was aiming at.
> It's a real shame I was scheduled to be speaking at the same time during
> EuroPython. :-(
Thats ok - I wasn't able to make it anyhow, Jml did a great talk though
- we worked on some of the slides together to kick start it:
> Are you submitting the talk to PyCon?
I hadn't, I'm hoping to do a lightning talk at PyConNZ. When is PyCon?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.idyll.org/pipermail/testing-in-python/attachments/20090922/1c7029b8/attachment.pgp
More information about the testing-in-python