- From: Mary Brady <mbrady@nist.gov>
- Date: Fri, 24 May 2002 11:31:37 -0400
- To: "Robert Clary" <bclary@netscape.com>, "Dimitris Dimitriadis" <dimitris@ontologicon.com>
- Cc: "Curt Arnold" <carnold@houston.rr.com>, <www-dom-ts@w3.org>
Comments inlined... -- Mary > > [bc] Representative tests I have been looking at include tests with: > > a) single data document (the vast majority of tests) > b) two data documents (about a half dozen) > c) tests which require the use of the embed tag to host the Adobe SVG > plugin. > d) the use of jsUnit test suites to combine individual test pages. > > I am not certain of the user interface of the test selection and > configuration page. It will consist of a form that should allow > selection of test suites or individual tests and overall configuration > choices for implementation (native, msxml3/msxml4, adobe plugin, etc) as > well as others. The form's action will be a GET to jsUnit's > testRunner.html passing the choices encoded in the url. > > My plan is to create a straw man that supports the following > implementations: native (browser's document), msxml3/4 active x > controls, adobe's svg plugin and the following: > > a test page for a single data document > a test page for two data documents > a test suite consisting of the two test pages > a test selection and configuration page > [mb] Okay. We need to load the following types of files: 1) xml 2) html 3) xhtml We also need to be able to toggle whitespace, entity expansion, and possibly validity. > These should allow us to determine the viability of the approach and the > scope of any modifications that will be required to the existing build > and xsl transforms. > > I plan to have this available for comment sometime this weekend. > > /Bob > >
Received on Friday, 24 May 2002 11:34:43 UTC