Re: what happened to JSUnit tests of dom level 3 load and save?
João Eiras <[email protected]> Thu, 01 Feb 2007 16:27:23 -0000
| Newsgroups | gmane.comp.web.dom.test-suites.general |
|---|---|
| Organization | feup |
| Message-ID | <op.tm2vzx1qjz3wb9@dragast> |
The test suites have always been broken for me.
See file
http://www.w3.org/2004/04/ecmascript/level3/ls/DOMBuilderTest0.html
It declares the following global variable, and manipulates it like this
var builder =3D null;
function setUpPage() {
(...)
builder =3D createConfiguredBuilder();
(...)
}
function DOMBuilderTest0() {
var success;
if(checkInitialization(builder, "DOMBuilderTest0") !=3D null) return;
(...)
var builder;
(...)
builder =3D =
lsImplementation.createLSParser(MODE_SYNCHRONOUS,NULL_SCHEMATYPE);
(...)
}
The problem is, the TC expects the builder variable that is passed to =
checkInitialization to be the object that createConfiguredBuilder return=
s, =
but that same function declares another var builder, which therefore hid=
es =
the global variable and creates a local undefined one, so all tests fail=
s.
I've mentioned this problem 4 months ago, and it still isn't fixed.
http://lists.w3.org/Archives/Public/www-dom-ts/2006Sep/0000.html
If the builder problem is fixed, then the function getResourceURI is =
undefined too.
Michal Domoslawski <[email protected]> escreveu:
> Hi,
>
> When I use JSunit form http://www.w3.org/DOM/Test/ to perform tests of=
=
> DOM level 3 Load and Save, progress bar is red and all tests return =
> errors. When JSunit loads "../level3/ls/DOMWriterTest4.html" it hangs-=
up =
> and nothing happens. I've testet it with Opera, FF2.0 and in both case=
s =
> results are the same. Weird fact is that when I've done the same thing=
a =
> week ago everything was fine and tests were passed. Are there any =
> chances that something was changed in DOMTestCase.js script and it =
> caused whole tests to return Errors?
>
> BR