their test case objects.  Created an automated tool, FixPathsAndIds.py,
to fix these.

TestCasePackager.py no longer throws when it encounters a non-*.js
file where it expects test cases.  Instead, it simply ignores it.

cases.

including https://bugs.ecmascript.org/show_bug.cgi?id=59.

for details.

module is now utilized.

rationale behind the addition of this file is it's meant to replace
TestCasePackager.ps1 outright and will be runnable on all major
operating systems.  There's still a bit of cleanup work needed as
the Python port was hardly optimized for the language.

A few side effects of this change:
- it now takes under ten seconds to generate the test262 website (PS
  version was taking over a minute)
- generated *.json files are ~5% smaller in size (PS was forcing
  '\r\n' and the Python version preserves the tests' newlines whether
  they're '\r\n' or '\n')

ES5 chapter.  That is, ecma-262-toc.xml now has '.0' sections for all chapters
and I've manually modified (Sputnik Ch. 13 & 14) test case id's and paths
to utilize the '.0' suffix.  Long term, SputnikConverter needs to perform
this transformation itself though.

to the following criteria:
1.  If a test case directory directly contains *.js files at the root level, package
    the entire directory as an XML regardless of how many *.js files are in
    subdirectories
2.  If the directory and subdirectories contain less than 1,000 test cases, package
    the entire directory as an XML.  Otherwise...
3.  Perform steps 1 and 2 on each subdirectory of the directory

The net effect of this change is that no test case XMLs are larger than 1.5 megs any longer,
although the total number of test XMLs has jumped from about a dozen to ~75.  This should
make running the test harness seem a little smoother across all browsers since we won't be
blocked downloading 4 meg files for several seconds any longer.

format.

that are expected to exist, but may very well now.

were actually unique across the test cases.  This *was* needed prior to November as we weren't
running each test case in it's own private global environment.  The situation now is that
we're running each test within it's own iframe => the modifications are no longer needed.

Few small improvements to SputnikConverter:
- App.config file locations have been fixed
- template files get pushed alongside generated tool binaries
- the root path for Sputnik conformance files is "Conformance", not "tests"
- allow the main exe to throw exceptions so they can be properly debugged with VS

some datetime constants before execution.  As we do not yet have support
for this, I've disabled them.  See https://bugs.ecmascript.org/show_bug.cgi?id=11
for more details.

Disabled.

"?sitedebug" to the end of the Test262 URL.

There's a mismatch between the Test262 test harness and IE Test Center's harness
which invalidated 15.4.4.17-5-1.js, 15.4.4.18-5-1.js, and 15.4.4.20-5-1.js on Test262.
Essentially what's going on is Test262 uses the 'window' object as 'this' for the test
case functions whereas IE Test Center uses the test case object housing the test case
function as this.  This causes problems for test cases pertaining to scoping.  I've gone
ahead and adjusted the Test262 tests to expect 'window' to be 'this', and will be updating
IE Test Center's harness to use the 'window' object as well so we don't run into this
problem again.

test\harness\helper.js:  extended the 'finished' method to accept as input the total elapsed execution time
                         of the tests.  Emit this to the activity bar


test\harness\sta.js:  too many years of Python had me thinking JavaScript arrays have an append method:)  Fixed.
                      Also, added a pickled representation of all test helper functions found in this file


test\harness\sth.js:  detached most test helper functions from the iframe's document object (as globals) and
                      inject these into the actual test cases. It's a bit slower and not as elegant, but it is
                      cleaner from an ES5 purist perspective.  Still need to move Sputnik helper functions into
                      sta.js

                      Extended Controller such that it now measures overall test execution time.  Such a change
                      is very useful for measuring performance-impact changes such as the aforementioned
                      improvement

- updated version number for the overall site to 0.3

Addressed test case issues detailed in https://mail.mozilla.org/pipermail/test262-discuss/2011-January/000020.html.

- default.html still had a reference to reports.js.  Removed.  Also, removed test\harness\reports.js
- test\harness\sth.js:  fixed a bug spotted by Mark Miller.  In short, we were allowing
  a test case return value of 'undefined' to be successful WRT IE Test Center tests because
  Sputnik tests normally return undefined (successful or not).  We now differentiate between
  Sputnik/IE Test Center when evaluating return values

- updated website version number to 0.2

Version numbers were incorrect on most *.html pages (referenced 1.0 and indicated the page was produced in October).  Fixed

Added a blurb to the "Development" section of default.html referring Ecma TC39 members to http://wiki.ecmascript.org/doku.php?id=test262:test262
for details on test submissions.

prior to the usage of "ES5Harness".  Specifically in cases like:
  var abc = ...;
  ES5Harness.registerTest( {
  //...abc gets used here

the declaration of "abc" would've been ripped out thereby corrupting the test.

This change fixes the issue for all existing IE Test Center and Sputnik test cases. Note
however that it could potentially fail for lines like this: "/*abc*/ /*".  If we ever add
cases including comments like this, the implementation of isTestStarted will need to be
revisited.

There were five such test cases that were being affected by this issue in IE Test
Center's chapter 10 and 15 tests.  These have all been fixed via the updated script.

for their adherence to the ES5 specs. Removing until we've fulfilled all internal policies
around these two tests.

- The only parameter required for this script is now the test suite version.  All other
  parameters are generated relative to the location of this script
- This script now generates the XML'ized test cases directly to website\resources\scripts\testcases\.
  Likewise, it copies the test harness taken from test\harness\* to website\resources\scripts\global\
- Added tons of error checking and we now emit the current generation status to stdout
- Made the script more generic in the sense that it can take arbitrary directories under test\suite\*
  containing ES5 test chapters.  Previous behavior was it was looking for test chapters directly under website\

access to the webpages.  index.html should suffice.

website\* out to test\*:
- Removed test\harness\ECMA-262-TOC.xml.  The casing on this file was incorrect, but
  more importantly it's a static file not generated by the harness
- Populated test\harness with the contents of website\resources\scripts\global\.  In
  the future, we need to update test\harness\* and propagate these changes out to
  website\*
- Test\suite\ietestcenter is now a verbatim copy of the IE Test Center tests that
  WERE under website\resources\scripts\testcases\*
- Moved all Sputnik tests from website\resources\scripts\testcases\* out to
  test\suite\sputnik_converted
- Moved website\resources\scripts\testcases\excludelist.xml out to test\config\*.  This
  particular file was only used for the test conversion process to XML, and is not actually
  needed by the website as best as I can tell
- Website\resources\scripts\testcases now only contains the XMLized test cases.  This is
  the right thing to do as the *.js files here weren't actually being used by the website
  and the general public can now peruse the test cases directly via Mercurial