I've been working on ticket #1668, to allow automated tests of quickstarted apps. I have some code which will do this, but I'm not sure the best way to integrate it into the TG2 "test suite".
Do we want to create projects from templates for each test? This would normally be the "correct" way to do testing, but with even a moderate number of tests, this will eat up a lot of time. Maybe create a project for each template and run a set of tests against it? This doesn't really adhere to the "correct" test methodology of isolating each test, but would take a lot less time. Or is there perhaps a way to make nose ignore the quickstart tests, except when specifically told to look for them? Thoughts? Opinions? Kevin Horn --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
