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.

#12 Oops - my mistake. Sorry.

by leafdigital

Wednesday November 22nd, 2000 6:19 AM

You are replying to this message

I must have missed those overall numbers - sorry. Kind of embarassing since I viewed it twice, once each browser... guess I looked at the bottom of the table, not the top.

As for making it clearer - I think it's clear enough (especially the 'by method' bit) and will be a useful resource for DOM programmers who might happen to come across the bugs and incompatibilities.

All I was really missing was the overall summary of current test results, rather like what you wrote here in fact - what the significant holes in compliance are for each browser. I think something like that would be useful, maybe for people who just want an 'executive summary' rather than to use it for programming.

Admittedly, you do then run the risk of being seen as partisan, or having your tests used as nothing more than a pissing contest between the two major browsers.