Test.Simple seems to have fallen out of maintenance and has several
problems I would like fixed. Having looked at the source code and
having been a user of this library for quite a while, I think it
would be to MochiKit's advantage to simply switch to something else.
The question is, what else? MochiKit's needs are pretty simple, but
if we're switching I'd like some additional features such as Rhino/
SpiderMonkey compatibility (preferably with a mock DOM
implementation). The tests will probably move out of HTML and
into .js files for this reason. Testing is basically all that's
holding up the 1.2 release, so I need to have this sorted out soon.
Can anyone provide recommendations for what I should look at and
why? Is there a need for Yet Another? It wouldn't be hard to build
a test framework on top of MochiKit.Base and perhaps MochiKit.Logging
(and I've already started to), but test runners and reporting is a
chore.
-bob
- [mochikit] JavaScript unit testing Bob Ippolito
-