Subj : Proposed Update to the JavaScript Test Library
To   : netscape.public.mozilla.jseng
From : Bob Clary
Date : Thu Feb 03 2005 08:43 am

I have been working on a modification
<https://bugzilla.mozilla.org/show_bug.cgi?id=263119> to the JavaScript
Test Library which would allow it to be run in browsers as well as via
the command line JavaScript or XPConnect shells.

Brendan has given a conditional "go ahead" to get these changes into the
tree if they reproduce the current results and do not adversely effect
the non-mozilla.org users of the Test Library.

You can run the tests online and read more about the modifications at
<http://bclary.com/2004/10/03/javascript-test-suite>. This includes a
description of the rationale behind the changes, a summary of the
changes, links to various diffs against the trunk and links to test
results. You can also download a 4 Mb zip file
<http://bclary.com/2004/10/03/js-tests.zip> containing the entire Test
Library.

Testing with Spidermonkey
=========================
I am confident that the new versions of the tests for the ecma, ecma_2,
ecma_3, js1_1, js1_2, js1_3, js1_4, js1_5 and lc2 suites reproduce the
current behavior of the trunk tests for spidermonkey when run using the
javascript shell. See:

<http://bclary.com/2004/10/03/js-tests/results-smopt-trunk.html>
<http://bclary.com/2004/10/03/js-tests/results-smopt-new.html>

<http://bclary.com/2004/10/03/js-tests/results-smopt-lc2-trunk.html>
<http://bclary.com/2004/10/03/js-tests/results-smopt-lc2-new.html>

Testing with Rhino
==================
The new version of the tests for ecma, ecma_2, ecma_3, js1_1, js1_2,
js1_3, js1_4, js1_5 and lc2 suites has one additional failure
(ecma_2/Exceptions/function-001.js) over the trunk versions using Rhino.
It is not clear to me if this is a failure in the new test or the old.
One good thing is that all lc2 tests in Rhino 1.6R1 pass for both the
new and the trunk tests.

I have been unable to get the lc3 tests to run and would appreciate
some help.

The new e4x tests result in 4 errors when run online in a Mozilla trunk
build. I have not been able to compare the new vs. old results for the
shell tests for e4x since I have been unable to build a JavaScript or
XPConnect shell that supports e4x. Any instructions on how to build an
e4x capable JavaScript or XPConnect shell would be appreciated.

If you have any objections to these changes in the JavaScript Test
Library, please make them known here. Otherwise these changes will be
checked into the trunk sometime in the not too distant future.

If you have any suggestions on how I can better test lc3 or build an e4x
aware javascript shell or xpcshell, please share them with me.

Bob

.