On Mon, Nov 14, 2011 at 5:12 AM, Edward K. Ream <[email protected]> wrote:
> Rev 4796 contains a long-overdue housecleaning.
> Running unit tests externally is a good indicator of the health of the
> leoBridge module, as well as an independent check of some of Leo's
> most important base classes.
As of rev 4798, all (enabled) unit tests pass when run externally. As
expected, just a few problems caused almost all the unit test
failures. A dozen or more tests are disabled when run externally, for
various not-too-important reasons.
Running unit tests externally is *much* faster than using a gui::
locally: 771 tests in 42.2 sec.
externally: 760 tests in 9.0 sec.
What I did:
- The nullGui now uses a fully capable string-based body widget.
- The nullGui now uses the regular undoer.
More work is coming:
1. At present, various frame classes all define local variations of
the high-level interface. This is a large violation of the Don't
Repeat Yourself principle. I would like to eliminate these repeats
using a single base class.
The requirement if that this common class **not** be a mixin class. I
have some ideas for how to do this while retaining single inheritance,
but it's not guaranteed to be feasible.
2. At present, the export tests produce empty files in
leo/test/unittest/output. This is a recent development, and is not
likely to be too serious.
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.
