I've added a couple of "full stack" tests to TG2 which create a real TG2 application via the standard configuration mechanisms, and test that it works. I'm not excited about the fact that we need to create folders for controllers, templates, and models, but pylons (and therefore tg2) gets the location of those folders from config, so it's worth testing that machenery.
Of course lots of this stuff is tested in the quickstart tests in tg.devtools, but I think it makes sense to add some tests to the tg server framework itself, since those tests are likely to be run more often, and since I don't want code in tg that only is tested by external packages if we can avoid it. I think the policy for TG2 tests in the framework should be that we test the framework itself, *and* it's integration points with all of our "core" dependencies. Given the tests that are already there, this should not be too hard to do. But before we go down this path too far, I want to see if other people think it makes sense to put these tests inside the framework itself, or should they be somewhere else? -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
