On Feb 28, 2007, at 2:48 AM, Mark Ramm wrote:
> So, many of our tests are very tightly coupled with the CP2 way of > doing things. But the actual TurboGears code is not nearly so > tightly coupled, and we are now able to process requests with a > quickstarted app (we get a stacktrace due to some configuration > work that isn't yet done, but we can fake it. > > Internal server calls need to change, and we probably need to > determin the API we want to use for mounting applicaitons at other > places than the root. Once we get things working in an acutal > applicaton, we plan to go back and write some new tests that are > less tightly coupled to CherryPy. Have you considered using paste.fixture for the functional tests? That would decouple the tests from CP completely as it treats the whole cow as an opaque WSGI app which is ideal IMO. I did some experiments with paste.deploy and CP3 a while back which I have here [1] if you guys want to take a peek. The paste.app_factory entry point that builds the CP3/TG WSGI app is implemented here [2]. Something similar can be done to create the app that needs to be fed to fixture's TestApp. Just some thoughts.... You guys are doing an amazing job out there at PyCON! (so great you're distracting me too much from this project that's keeping me away from the world) Keep it up! (and leave some coding to do for the poor souls who cannot join you now... =) Alberto [1] http://tinyurl.com/332ad9 [2] http://tinyurl.com/tjhb8 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
