On Jan 7, 2008 11:48 AM, Mark Ramm <[EMAIL PROTECTED]> 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: > > > > * 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. 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. >
That's cool... I realize that tg2 needs to pick a default & right now the sane choice is paste.fixture. On the other hand, you can't blame me for wanting to change the dynamic by bringing some of Ian Bicking's great ideas to the masses with improvements to twill. Today, access to the wsgi environment. Tomorrow, perhaps a more pythonic API. :-) I started down this path because of the problem above, and because testing identity-driven sites in tg1 is more difficult than it needs to be (yes, I've seen thesamet's blog). If I'm successful and it becomes a part of TG 2 eventually, I'll be ecstatic, but my primary purpose is to scratch an itch that I have today. > > 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 > Agreed. wsgi_intercept is a brilliant idea (another one of Ian's), with a nice implementation from Titus. A few more bits of randomness: 1) I'm working toward a testutil replacement using the twill enhancement I mentioned. I hope to be able to use it in tg1, tg2, and the cherrypy3 branch. 2) Since twill enjoys wide adoption, users of other frameworks have probably been exposed to it, and many are using it already. I'd like for them to be able to keep their tests intact as possible as they move to TG. 3) I'm concerned that there are a lot of people that don't have unit tests for their TG 1 apps, and they'll perhaps have a harder time switching to TG 2 than they should. twill-script provides a quick mechanism for adding tests to an existing site. 4) I'm going to be hacking around on this during the sprint this weekend. Thanks for the response! -Ken --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
