On Jul 8, 2:55 pm, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> The code works well enough to pass a toy unit test... The shadow branch now contains the first-ever usable unit-testing framework for @shadow. Here is the commit message: QQQ A giant step forward. We now have an outline-based unit-testing framework for shadow files: test.leo contains @suite run @shadow-test nodes in the @shadow-tests tree. This @suite node creates and runs leoShadow.atShadowTestCase tests or each @shadow-test node in the @shadow-tests tree. Thus, creating a new unit test is as easy as creating the following tree: @shadow-test old new The atShadowTestCase.setup method computes creates old and new public and private lines, as well as an expected_results list. At present, there are 10 tests covering insertion, deletion and replacing of single lines in a single node. All these tests pass, except the last test. QQQ I should add that the old and new nodes can be full trees, although at present they are only single nodes. BTW, the failing unit test is '@shadow-test insert after last line', an important boundary condition. Edward P.S. The next step will be to improve the tracing produced by the unit tests. I strongly suspect that all efforts in this area will pay off. Still the present testing code is already informative... 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 -~----------~----~----~----~------~----~------~--~---
