Hi, On 7/18/07, Agustin Villena <[EMAIL PROTECTED]> wrote: > > Hi! > Yesterday I was playing with the new nose (0.10a1), testing the > htmloutput plugin, and then I imaginated a new feature of pylons: "What If > the nose testrunner was 'embedded' in pylons?". Pylons right now has a > powerful debugger and interactive shell embedded on it... and we can make > them to work together.
Interesting idea. Let me explain: > > - Every pylons app must have a new controller : testrunner. In its most > simple form it only has a button: "Run Application Tests" > - When tests runns, we have a display with the traditional look we have > int test-runners GUIs: a list of tests with red-green state > - In the failed test, we can navigate to the source code, and even attach > the pylons' debugger > > Well, my question is: any hint to help me begin developing this idea? Nose has good API to drive tests programmatically. You can use it to run the tests. As for introspection for failed tests, I think you need to dig into EvalException middleware (part of Paste) to see how it works it magic. HTH, Max. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
