W3C home > Mailing lists > Public > www-dom-ts@w3.org > May 2002

Re: Status check

From: Curt Arnold <carnold@houston.rr.com>
Date: Fri, 24 May 2002 00:39:07 -0500
Message-ID: <011401c202e5$52e7bb40$a800a8c0@CurtMicron>
To: <www-dom-ts@w3.org>
Robert Clary wrote:
> Ok. I will put together an example and post it so we can use it as a
> straw man for discussion.

My first inclination is to allow a JSUnit test page to be able to provide a
configuration page in a frame.  Something like:

1) Select the test from the browse button
2) The contents of the configuration page appears in a frame below the test
selection.  The page would allow you to select implementation and
configuration (validating/non-validating, preserve entities/expand entities,
etc).  The configuration page for the test would either be implied from the
filename or might be determined by loading the test and evaluating a
3) When the test is run, a JSUnit method can be used to obtain the
configuration document.

Whether that is possible cross browser, I don't know.

The boilerplate DOM TS code should hide all the gore from the DOM test
itself.  The tests should be oblivious to the details of implementation
Received on Friday, 24 May 2002 01:39:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:05 UTC