DOM Level 2 Conformance Test

Monday November 20th, 2000

Bob Clary writes, "I have written a DOM Core Level 2 Conformance test which can be run with both Mozilla/Netscape 6 and Internet Explorer 5.5. It uses only the DOM methods and does not depend upon the HTMLDocument or the XML Parser. The test coverage is not yet complete but is nevertheless extensive. I think you will find the results interesting.

"The test generates two sets of reports: one by test case and one by API name. It is completely interactive and contains links to the relevant parts of the DOM Core 2 Recommendation as well as links to bug reports in Bugzilla. Of course there are no links to reports of Internet Explorer bugs available.

"If you run all of the tests it will use 50-60M and may take several minutes depending on your processor so be patient. If you do not have enough memory to run all of the tests at once, you can choose a subset of the test cases to run.

"If you have any problems, questions or suggestions please feel free to contact me."

UPDATE: The host for the conformance test is taking down the site due to heavy bandwidth usage. We'll let you know when the site's back online.

#2 Re: Care to explain those "interesting" results?

by rdc

Monday November 20th, 2000 10:46 AM

You are replying to this message

I left it to you to make the comparisons. I will give a brief summary of my opinion if you wish.

Essentially it appears that IE 5.5 (on Win32 at least) supports a good deal of the DOM 1 Recommendation which is what is claimed from their hasFeature. They do not implement DOMException at all and throw their own Exceptions which accounts for their failures of the Exception tests. In addition, IE does not implement portions of the DOM API which in practice are not used. For example, Comment does not have children and IE's support for that portion of Comment's interface is lacking.

Mozilla supports the DOM 1 and the DOM 2 Core to a greater extent than IE 5.5 on Win32. It has not implemented all of the Namespace related methods however and has other Namespace related problems.

Both IE and Mozilla report null strings instead of null values for several attributes.

As to your comment that there are no "overall" numbers and no "specific" information about the methods, I point you to the first row in the API report where the over all numbers are reported.

Each test case is listed where you can click on the link and view the entire test case and it's results.

In addition, clicking on the + sign in from of the API Names in the API report will display a list of specific tests which can be displayed for that API Name.

Links to the DOM Core 2 Recommendation as well as links to Bugzilla are provided as well.

This was described in the documentation of the Conformance tests in general and specicially in the DOM Core 2 tests. Was the explanation not clear ? Do you have suggestions on what additions I can make to make this clearer?