W3C home > Mailing lists > Public > www-dom-ts@w3.org > February 2007

Re: what happened to JSUnit tests of dom level 3 load and save?

From: Joćo Eiras <joao.eiras@gmail.com>
Date: Thu, 01 Feb 2007 16:27:23 -0000
To: "Michal Domoslawski" <michal.domoslawski@comarch.com>
Cc: "www-dom-ts@w3.org" <www-dom-ts@w3.org>
Message-ID: <op.tm2vzx1qjz3wb9@dragast>

The test suites have always been broken for me.
See file

It declares the following global variable, and manipulates it like this

var builder = null;

function setUpPage() {
      builder = createConfiguredBuilder();

function DOMBuilderTest0() {
	var success;
	if(checkInitialization(builder, "DOMBuilderTest0") != null) return;
	var builder;
	builder =  

The problem is, the TC expects the builder variable that is passed to  
checkInitialization to be the object that createConfiguredBuilder returns,  
but that same function declares another var builder, which therefore hides  
the global variable and creates a local undefined one, so all tests fails.
I've mentioned this problem 4 months ago, and it still isn't fixed.

If the builder problem is fixed, then the function getResourceURI is  
undefined too.

Michal Domoslawski <michal.domoslawski@comarch.com> 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 cases  
> 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
Received on Thursday, 1 February 2007 16:27:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:07 UTC