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

Re: Running HTML L2 with Mozilla 0.9.9 and later

From: Rick Rivello <richard.rivello@nist.gov>
Date: Mon, 8 Apr 2002 10:12:55 -0400
Message-ID: <00d801c1df07$7abb87c0$573b0681@sdct.nist.gov>
To: <www-dom-ts@w3.org>
I ran the tests after editing alltests.html and am now only
getting 14 failures out of 427 tests.  I also had to comment
out the (2)HTMLOptGroupElement* and (13)HTMLSelectElement*
tests that currently have bug reports filed by Curt.

I am in the process of checking the tests to see if the problem is with
the test or the implementation.

Curt can I also take the same approach with the html_alltests.html file
so that I can run the tests on IE?

Here are the results

3. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLAppletElement05
failed

"codeBaseLink"
Expected ./files/ (string) but was http://xw2k.sdct.itl.nist.gov/brady/dom/files/ (string)

10.
file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLButtonElement01
failed

"formLink"
Expected form2 (string) but was  (string)

15. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLElement01
failed

"idLink"
Expected Test-HEAD (string) but was  (string)

16. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLElement30
failed

"titleLink"
Expected HEAD Element (string) but was  (string)

17. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLElement59
failed

"langLink"
Expected en (string) but was  (string)

18. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLElement88
failed

"dirLink"
Expected ltr (string) but was  (string)

19. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLElement117
failed

"classNameLink"
Expected HEAD-class (string) but was  (string)

21.
file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLFieldSetElement01
failed

"formLink"
Expected form2 (string) but was  (string)

24. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLFormElement03
failed

"nameLink"
Expected form1 (string) but was  (string)

29. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLHtmlElement01
failed

"versionLink"
Expected transitional 4.0 (string) but was transitional xhtml 1.0 (string)

32. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLInputElement08
failed

"checkedLink"
Call to assertTrue(boolean) with false

34.
file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLIsIndexElement01
had an error

Error message is:
"TypeError: fNode has no properties"

39. file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLLinkElement01
failed

"disabledLink"
Call to assertTrue(boolean) with false

58.
file:///C:/cygwin/home/Administrator/2001/DOM-Test-Suite/build/level2/html/ecmascript/tests/alltests.html:testHTMLTableRowElement07
failed

"bgColorLink"
Expected #00FFFF (string) but was #00ffff (string)


----- Original Message -----
From: "Arnold, Curt" <Curt.Arnold@hyprotech.com>
To: <www-dom-ts@w3.org>
Sent: Friday, April 05, 2002 3:58 PM
Subject: RE: Running HTML L2 with Mozilla 0.9.9 and later


> Thanks Rick.
>
> That appears to mean that anchor.xml isn't loaded until after the first test
> has completed.  This might be the same problem that causes Mozilla to have
> slightly different results for the DOM L1 Core tests.  In that case, the
> test failure count would only vary by +/- 1, but then the DOM L1 Core tests
> only loaded one XML document and the HTML tests load 20 or so.
>
> You might try editing alltests.html and take the first test of each "family"
> and duplicating it and calling the first one something like,
> "testHTMLAnchorElementXX" and run the test again and ignore any test
> failures on the XX tests.  That should at least clarify which tests are
> really failing and which ones might be being run before the document has
> been completely loaded.
>
> Fixing the problem will require taking advantage of the pretest hook that
> Bob Clary was adding to JSUnit or finally getting the custom runner working.
>
>
> > -----Original Message-----
> > From: Rick Rivello [mailto:richard.rivello@nist.gov]
> > Sent: Friday, April 05, 2002 12:26 PM
> > To: Curt Arnold; www-dom-ts@w3.org
> > Subject: Re: Running HTML L2 with Mozilla 0.9.9 and later
> >
> >
> > Here's the results from running the tests
> > on Mozilla 0.9.9.
> > __________________________________________________________
> >
> > I first ran  HTMLAnchorElement01 test by itself
> > and got the error:
> >
> >  "Asize"
> > Expected 1 (number) but was 0 (number)
> > ___________________________________________________________
> >
> > I then put two entries in the alltests.xml file
> > HTMLAnchorElement01 and HTMLAnchorElement02.
> >
> > I still got the same error as above for HTMLAnchorElement01
> > and HTMLAnchorElement02 ran successfully.
> > ____________________________________________________________
> >
> > I then ran the same two tests again changing the order in the
> > alltests.xml file. HTMLAnchorElement02 first and
> > HTMLAnchorElement01 second.
> >
> > This time HTMLAnchorElement02 received the Asize error and
> > HTMLAnchorElement01 ran successfully.
> >
> >
> >
> > Rick
> >
> > ----- Original Message -----
> > From: "Curt Arnold" <carnold@houston.rr.com>
> > To: <www-dom-ts@w3.org>
> > Sent: Friday, April 05, 2002 10:54 AM
> > Subject: Re: Running HTML L2 with Mozilla 0.9.9 and later
> >
> >
> > > Rick wrote:
> > > This error looks similar to what was happening with some of
> > the tests
> > > in IE. It fails the Asize check for HTMLAnchorElement01 and
> > passes the
> > > Asize check for HTMLAnchorElement02.  Both tests are using the same
> > > file so I don't understand why one would pass and one would fail.
> > >
> > > Do they fail when run in isolation?  I don't have time to
> > check right
> > > now. If they work in isolation, but fail in when run in the
> > suite, a
> > > test might be lying about whether it modifies its test
> > document and a
> > > subsequent test gets a corrupted test document.
> > >
> > >
> > >
> >
>
>
Received on Monday, 8 April 2002 10:12:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:46 GMT