<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
<font size="-1">Hi,<br>
<br>
Here are a couple of suggestions which, in my opinion, would help
the community work:<br>
- test262.ecmascript.org<br>
-- In the Results page, it would be useful to have a link to the
test file in the <a class="moz-txt-link-freetext" href="http://hg.ecmascript.org/tests/test262/">http://hg.ecmascript.org/tests/test262/</a> website
(may help to spot differences between the run test suite and the
latest )<br>
-- A "report a bug" link next to each bug result (or in the
"source" popup?)</font><font size="-1"> would be useful too</font><font
size="-1">. If there is such a feature in Bugzilla, the link could
carry a preformatted bug title and pre-fill the bug report to
point to the "Tests" component. Uniform bug titles make
text-search easier.<br>
<br>
- Test searching<br>
There are now about 10000 tests. By default, they are sorted in
the repo by source(Sputnik |
ietestcenter)/chapter/section/subsection/...<br>
Even if it certainly makes sense from a test suite producer point
of view (and directory choices has to be made anyway), it doesn't
cover all search use cases. In order to "identify test holes" more
efficiently as suggested under "Community Contributions" it would
be helpful to have some tool to search for tests. For instance,
it's currently hard to find if a test has been forgotten
regarding:<br>
* native prototype objects<br>
For instance, in 15.4.2.2 is written "The [[Prototype]] internal
property of the newly constructed object is set to the original
Array prototype object, the one that is the initial value of
Array.prototype". There is clearly a test to write based on that
to make sure that Monkey-patched Array.prototype aren't used. Such
a pattern can be found for functions (15.3.3, 15.3.4), objects
(15.2.2.1 step 4) and certainly in other places.<br>
* length properties<br>
* Errors (make sure that code that should throw errors have a test
for them)<br>
* strict mode (I assume it's not going to be covered in a chapter)<br>
* Any other cross-chapter topic you could think of.<br>
Several different approaches could be taken to tackle that issue:<br>
-- text-search<br>
-- tags search<br>
<br>
<br>
- Run partial test suite<br>
Running the test suite is currently long. I'm currently reviewing
FF4 fails. When I close my web browser, I have to re-run all
tests. However, most of the time, I don't care about most of them.
I just want all those that I haven't reviewed yet. I wish the
website could offer an easy way to run for instance:<br>
- all chapter 15.2 tests (or any chapter/section/subsection
obviously)<br>
- all tests found through a search (if/when some search feature
will be available)<br>
- all tests that has been added or changed between two test suite
versions. If I have reviewed all tests of version x, I may not
care about them when the x+1 version comes out.<br>
<br>
<br>
- Accept user contributed tests<br>
I have read that "Ecma’s intellectual property policies, permit
only Ecma members to directly contribute code to the project.". I
however think that this test suite would benefit from accepting
contributions from the community. No one ignore how big is the
JavaScript community on Github. No one ignore how crucial is
JavaScript to the world as it is the most used programming
language. I think there is a need to open up the way tests can be
contributed.<br>
If the E</font><font size="-1">cma’s intellectual property
policies cannot be changed/adapted to make that happen, could ECMA
TC-39 members find a way to accept user contributions, review them
and then submit them to Ecma? For instance, by creating a TC-39
github account and a test repo, people create tests, submit them
to this repo and when there are enough of them or after a certain
amount of time, </font><small>TC-39 members officially submit the
tests to ECMA. There are certainly intellectual property/copyright
issues that has to be considered, by I'm drawing some sort of main
idea.<br>
<br>
I'd be happy to help out if there is anything I can do to help
with<br>
</small><font size="-1"><br>
David<br>
</font>
</body>
</html>