Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Testing form submittal
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Kumar McMillan  
View profile  
 More options Jan 7 2008, 2:02 pm
From: "Kumar McMillan" <kumar.mcmil...@gmail.com>
Date: Mon, 7 Jan 2008 13:02:20 -0600
Local: Mon, Jan 7 2008 2:02 pm
Subject: Re: [TurboGears] Re: Testing form submittal
On Jan 7, 2008 11:48 AM, Mark Ramm <mark.mchristen...@gmail.com> wrote:

> > Here's a brief comparison of twill & paste.fixture based on my current
> > understanding:

> > twill:
> > + good documentation (there's even a short book)
> > + wide adoption. 78k vs 2k hits in a simplistic googlefight [2].  I've
> > encountered examples of using twill with CherryPy, Turbogears, Django, Zope,
> > Pylons, etc. during my wanderings.
> > + twill-sh can be used as a test recorder.  There's also a maxq extension,
> > but I'm not sure what it's current state is.

> > paste.fixture:
> > + access to wsgi environment makes testing controller results possible.
> > + nice pythonic API.
> > + pylons uses it, and tg2 will be based on pylons.

> > Other notes:
> >   * Several times using twill, I've felt that the exceptions haven't been as
> > informative as they could be.   I haven't used Paste enough to draw a
> > comparison there.

> >   * I've hacked up twill to support access to the wsgi environment using
> > wsgi_intercept [3], but Titus naturally wants me to clean it up before
> > accepting it.  I plan on working on it more this weekend.

> I definitely think we should support both Twill and paste.fixture in
> TurboGears 2, but we need to pick a default, and I think that
> paste.fixture offers the path of least resistance for TG2.

why not jump right into webtest?
http://pythonpaste.org/webtest/

It adds yet another requirement but this is the next generation of
paste.fixture so it will be better maintained and already offers some
nicer features plus an even more pythonic interface.  One nicety is
how it integrates with lxml.html to provide xpath and other useful
access to HTML docs (even tries hard to support broken or janky
markup).  This is not required, btw, and will "not work" gracefully if
you don't have lxml.html installed.  Note that this specific feature
also requires lxml2, which may still be in beta.

Kumar

> And I've
> been working with it quite a bit recently, and it seems to be very
> pythonic, reasonable, and I'm sure that we will be able to make
> testing a lot nicer in tg2 than tg1 was.

> Having a good set of twill+wsgi intercept recipies will be a huge boon
> to TurboGears and Pylons users, as it would be nice to be able to
> write some tests that sometimes run in process and sometimes run
> against the full server stack -- for instance when writing "deployment
> tests" that verify that a given deployment setup actually works ;)

> --Mark


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.