On Mon, Nov 17, 2008 at 9:36 AM, tfer <[EMAIL PROTECTED]> wrote: > ...my code exists only in a leo outline, > and gets called via a button, (at least until it gets packaged into a > true plug-in), so I need a way to support testing in this, "non- > modularized" usage. Leo itself uses unitest, but here the test code > is contained in test.leo and works on Leo which is already loaded. > > Any hints on using this for my use case?
The run-unit-tests command is probably what you want. It creates dynamicUnitTest.leo by copying all the @test and @suite nodes in the selected outline, then runs dynamicUnitTest.leo in such a way (I forget how :-) that it runs all unit tests. So this works even while you are changing code: the last saved code will be in effect. The run-all-unit-tests command does the same thing, except it copies all @test and @suite nodes to dynamicUnitTest.leo, not just those in the presently-selected tree. Please try this and report any problems. I haven't used it lately, and a small test threw an AttributeError for nullButtonWidget.bind. I'll fix this immediately. 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 -~----------~----~----~----~------~----~------~--~---
