On Dec 12, 9:33 am, "Edward K. Ream" <[email protected]> wrote:
> I have begun work on the serious bugs, starting with a clone bug. A > proposed fix made a new unit test pass, but other tests started > failing. This may be a problem with the unit tests themselves, but in > the new world order everything must be sorted out before I push > anything. After 2 or 3 calendar days (about 4-6 hours real work) I discovered that an @shadow unit test was deleting leo\test\unittest\.leo_shadow, with predictably tragic results for any @shadow files used in the unit tests. Sheesh. Moreover, the "real" fix, that is the change to fc.getLeoOutlineFromClipboard, had further bugs, not caught be the new unit test that demonstrated that the new code fixed the original problem. In other words, a quick and dirty unit test for a significant fix was not nearly good enough. A more systematic approach is needed for methods like fc.getLeoOutlineFromClipboard. So it may take a day more to wrap up this particular bug. 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.
