> 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.
This sounds like a great idea. If we had a stable test interface between TG1 and 2 (and some hopeful CherryPy3 version of TG) that would be amazingly helpful for people as they migrate forward. And I was never super-excited about the way we monkeyed arround with cherrypy internals to get the TG1 test interface, and it's slowed us up more than once when we tried to do the CherryPy 3/1.1 work, and again when thinking about the TG2 upgrade path. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
