RE: HTML DOM Test Case Incorrect (HTMLDocument03.html)

Glad to see you participating

> So I seem to have got rather behind here due to other commitments, so 
> apologies for this feedback coming rather late. However I feel that 
> importing testsuites that are designed for other/older specifications is 
> generally a bad approach. I suspect that even once such testsuites have 
> been adapted to HTML5 they will retain traces of the older 
> specification; that is they will tend to test requirements that were 
> present in the old specification but ignore ones in the new 
> specification, they will tend to have bugs relating to changed 
> requirements, and so on. It strikes me that adapting such a testsuite 
> will be at least as much, if not more, work than systematically creating 
> a new testsuite of the same quality from scratch based on the actual 
> text of HTML5.

The plan is to remove/update tests that are incorrect per the HTML5 spec.
The pages have been initial checked in w/o any updates.  I did this so one can follow the change log to see what the changes were from the original test cases.

See -> http://lists.w3.org/Archives/Public/public-html-testsuite/2010Feb/0009.html
See -> http://lists.w3.org/Archives/Public/public-html-testsuite/2010Feb/0012.html


> In the specific case of the DOM2 test suites, I also think that the 
> dependence on jsUnit is a significant problem; my experience is that it 
> is rather heavyweight, hard to use, and difficult to understand if 
> something goes wrong.

I agree that is why I added a test loader page to HG.  It gets rid of all the jsUnit dependency and I added a console.log to the assert code.

Try -> http://dvcs.w3.org/hg/html/raw-file/tip/tests/submission/Microsoft/htmldom/loader.html?area01.html


-Kris

-----Original Message-----
From: public-html-testsuite-request@w3.org [mailto:public-html-testsuite-request@w3.org] On Behalf Of James Graham
Sent: Thursday, March 11, 2010 2:55 AM
To: public-html-testsuite@w3.org
Subject: Re: HTML DOM Test Case Incorrect (HTMLDocument03.html)

On 02/16/2010 01:53 AM, Kris Krueger wrote:
> At the last conf call, we discussed leveraging the older DOM HTML Test Suite for the HTML5 Test Suite.
> Since that meeting I have been reviewing the test cases from this test suite looking for interop problems.
>
So I seem to have got rather behind here due to other commitments, so 
apologies for this feedback coming rather late. However I feel that 
importing testsuites that are designed for other/older specifications is 
generally a bad approach. I suspect that even once such testsuites have 
been adapted to HTML5 they will retain traces of the older 
specification; that is they will tend to test requirements that were 
present in the old specification but ignore ones in the new 
specification, they will tend to have bugs relating to changed 
requirements, and so on. It strikes me that adapting such a testsuite 
will be at least as much, if not more, work than systematically creating 
a new testsuite of the same quality from scratch based on the actual 
text of HTML5.

In the specific case of the DOM2 testsuites, I also think that the 
dependence on jsUnit is a significant problem; my experience is that it 
is rather heavyweight, hard to use, and difficult to understand if 
something goes wrong.

As a more general point, it seems this issue was discussed in a telecon 
and presented to the list and then acted on as a fait-accompli. 
Obviously you are free to work on any tests that you like so in this 
case that is not too significant. However in general I hope that all 
important discussions and decisions happen on the mailing list where all 
interested parties can participate in an asynchronous manner. It is 
simply not possible for everyone to attend the telecons, nor do they 
provide the best environment for making well reasoned arguments.

Received on Friday, 19 March 2010 16:44:10 UTC