On Oct 31, 8:34 am, "Edward K. Ream" <[email protected]> wrote: > As of rev 4690, Leo supports "hidden" unit tests. This just may be > the missing piece of Leo's unit testing arsenal.
The more I use hidden unit tests, the less I like them. It's frustrating: the are *almost* exactly what is wanted, but not quite. The "reload" problem keeps biting. Yes, the exact code being tested gets redefined every time the unit test runs, but I often change *other* code while developing and testing new code, and that *other* code doesn't get reloaded. So it looks like this "great new pattern" doesn't really work. Boo hoo. My new/old work flow is to create @test nodes in ekr.leo, a fairly small personal file. I can reload this file very easily and quickly as I change the code under test. When I'm done with a unit test, I'll just copy it to unitTest.leo. Edward P.S. Awhile back I improved the execute-script command so it would do a better job of setting things up so that pdb could actually see the scripts sources. It looks like similar work is needed to that pdb will be able to see sources in unit tests. I plan to do this asap. EKR -- 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.
