Excerpts from Danny Navarro's message of Thu Dec 30 16:33:02 -0300 2010:
> On Thu, Dec 30, 2010 at 8:24 PM, Mariano Mara <[email protected]> wrote:
> > Excerpts from Marius Gedminas's message of Thu Dec 30 15:55:33 -0300 2010:
> >> On Thu, Dec 30, 2010 at 01:41:45AM -0500, Chris McDonough wrote:
> >> > I've been ignoring the fact that WebOb has very light test coverage for
> >> > a while now, but I've just run into a bug that makes it clear that my
> >> > blissful head-in-the-sand days are nearing an end.
> >> >
> >> > Is anyone interested in leading a task to give WebOb 100% test coverage?
> >> > It's a fairly large task, inglorious, and boring, but straightforward
> >> > and will help *lots* of people inside and outside the Pylons community.
> >> >
> >> > If so, please respond here.
> >>
> >> I wouldn't mind giving this a push, if time permits.
> >>
> >> The upstream repository is https://bitbucket.org/ianb/webob/.  I suppose
> >> we should submit patches via bitbucket pull requests?
> >>
> >> Marius Gedminas
> >
> > That's how I did it so I hope you're right. I already added tests for
> > webob.html_escape and webob.datetime_utils and I'm working on
> > webob.cookies right now [1].
> >
> > Would you like to lead and distribute the workload? It would be great so
> > we can prevent duplication of effort.
> 
> Count with me for the distribution of workload.
> 
> I would need some canonical examples of how you want to write the
> tests. I guess we are talking about writing unit tests with unittest
> instead of extending the current doctests.

As far as I can tell from the original tests, nose.tools is the weapon of
choice. Besides the tests Gael provided, I don't see unittest in use.

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pylons-devel?hl=en.

Reply via email to