W3C home > Mailing lists > Public > public-mwts@w3.org > March 2007

Re: Getting help on DOM Test Suite?

From: Curt Arnold <carnold@houston.rr.com>
Date: Tue, 6 Mar 2007 12:30:54 -0600
Message-Id: <D55810D9-7C2E-4401-814B-5D9F0BE83D49@houston.rr.com>
Cc: Dominique Hazael-Massieux <dom@w3.org>, public-mwts@w3.org
To: Carmelo Montanez <carmelo@nist.gov>

You may be more interested in the self-hosted production which takes  
the tests and converts them to a corresponding set of HTML, XHTML or  
SVG documents.  Each document runs a test script on load and then  
modifies its document model to report either success or failure.  The  
WebKit project (open-source Safari) uses the self hosted productions  
in its unit tests.  The self-hosted productions were never endorsed  
by the DOM WG and the results were never fully compared to those run  
using JSUnit.

To build test self-hosted tests:

ant dom1-core-gen-selfhtml

where you can replace "dom1-core" with "dom2-events", etc, and  
"selfhtml" with "selfxhtml" and "svgunit".  To run a test, load one  
of the produced documents (for example, build/self-hosted/html/level1/ 
core/documentgetdoctypenodtd.html.  An alltests.html is provided that  
runs the individual tests in an embedded frame.





On Mar 6, 2007, at 9:07 AM, Carmelo Montanez wrote:

> Hey Dom:
>
> I spoke with both Mary Brady and Rick Rivello from my end.  I am  
> also copying Curt Arnold here,
> who was heavily involved in the development of the tests/harness.  T
>
> The tests are defined in terms of XML (each test is an XML  
> instance).  So if there
> is a way you can simply transform the tests into whichever format  
> fits you, then
> you can easily run them.  The running format given on the web site is
> suite better for desk tops (as it deals with jsunit and the like) 
> and I can see how
> easily you can get into hot water with memory issues.
>
> I am sure Curt have some more insights into this.
>
> Carmelo
>
>
> At 11:15 AM 3/5/2007, Dominique Hazael-Massieux wrote:
>
>> Hi Carmelo,
>>
>> I've tried to run the DOM Level 1 test suite [1] on a combination of
>> mobile devices/user agents, but without much success; from what I can
>> tell, the test harness relies on frames and iframes, is very  
>> memory- and
>> cpu-hungry, and requires some good enough level of javascript that  
>> makes
>> it hard or impossible to run on quite a few mobile devices available
>> today.
>>
>> I've made a few attempts at diving into the test cases to see how we
>> could re-use them in a more mobile-friendly manner, but the  
>> current set
>> up, while very efficient for desktop browsers, make it a bit hard to
>> figure out how to re-use the existing test cases in a different test
>> harness.
>>
>> As NIST was heavily involved in the development of that test  
>> suite, esp.
>> Mary Brady, I was wondering if you could get some input or leads  
>> as to
>> how we could re-purpose these test cases in a new harness.
>>
>> As an example of a simple set of test cases that do run on my  
>> phones and
>> that test a subset of javascript (including a few DOM functions):
>> http://paxmodept.com/pan/javascript/javascript.xhtml
>>
>> Thanks,
>>
>> Dom
>>
>> 1.
>> http://www.w3.org/2004/04/ecmascript/jsunit/testRunner.html? 
>> testpage=http://www.w3.org/2004/04/ecmascript/level1/core/ 
>> alltests.html&implementation=iframe&skipIncompatibleTests=true&autoRu 
>> n=true&contentType=text/html
>
Received on Tuesday, 6 March 2007 18:31:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:07 GMT