On Wed, Mar 25, 2009 at 10:17 AM, Edward K. Ream <[email protected]>wrote:
> > > On Wed, Mar 25, 2009 at 8:42 AM, zpcspm <[email protected]> wrote: > >> >> it looks like using @test nodes in a Python project ties the process of >> running them to leo >> itself. > > > This seems to be the theme of the month. > > People want all of Leo's advantages without Leo. > I can think of two possible approaches. 1. Run unit tests in the Leo bridge. 2. Create a script that will convert @test nodes to stand-alone unit tests. It's doable. The script will do explicitly what @does implicitly, that is, create explicit instances of class generalTestCase(unittest.TestCase) . The interesting part is converting **tree data** (usually, but not always, children of @test nodes) to data that can be accessed in some way. Typically, @test nodes use g.findNodeAnywhere and g.findNodeInTree to access tree data. @suite nodes might be harder. Maybe they would have to be converted by hand to @test nodes... Edward --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
