RE: ECMA harness

>If a developer is testing their implementation, they will be required to
>run every test every time.  Allowing developers to test small portions
>of their implementation is a much more efficient use of time.

As long as the test harness provides _some_ configurable mechanism for
selecting which tests do and don't run, your needs would seem to be
addressed. Whether than mechanism is exclusion lists to block everything
you're currently uninterested in, or predefined groups, or some other form
of magic doesn't seem to make much practical difference...?

______________________________________
Joe Kesselman  / IBM Research