failed.

Much rougher: A first attempt at building the testcases for the website based on the new canonical test262 style testcase.

- a lot of JS harness code written in strings have been moved out to actual physical files
  such as ed.js (syntax error detection for globally scoped tests) and gs.js (global scope test
  case validator).  This change makes it far easier to maintain the test harness code
- reorganized helper.js providing a clear indication which methods are used by external objects,
  which are implementation details, and which are unequivocally test262-specific.  I've also added,
  openErrorWindow, which will be used to open a descriptive error message window for each test case
  failure reported on the 'Run' tab
- improved the error message for syntax errors occurring when a test case fails to load
- sta.js no longer tries to pickle all helper functions it contains!  Instead, we load the file
  directly from sth.js.  The performance of fnGlobalObject has been improved.  Finally, the ES5Harness
  object has been moved from sth.js (in a string) to here
- sth.js now has a browser implementer hook, controller.implementerHook, which allows browser implementers
  to handle test case failures in their own way (e.g., log to the filesystem).  The 'run' function was
  basically re-written

Added 37 new test cases from the "IE Test Center" Build release.  There were 14 modifications to
existing test cases as well.  Refactored SputnikGlobalScope.js such that test case paths are now used
as indices into the GlobalScopeTests array.

TestCasePackager.py had the concept of templated test harnesses introduced - see templates\runner.test262.html.
Also added support for one HTML test harness per ES5 chapter.  Last but not least, TestCasePackagerConfig.py
now has a 'source control' abstraction class which abstracts away source control adds|edits when dynamically
generating *.json and *.html test chapters.

15.4.4.15-3-14, 15.4.4.15-3-29, and 15.4.4.15-3-8 were disabled with no reason or bug given. These actually look OK,
and pass on all browsers...

Disabled 9 invalid tests.

on the live website to be sure.

host objects (which make them invalid for test262).  Using this, I found one benign 'alert'
usage (it was never even called) and removed it.

New Sputnik 'negative' metadata that included exception type was causing problems for SputnikConverter.
Took the easy fix and split the metadata into two: 'negative' and 'errortype'.

- 22 test case additions (mostly strict mode)
- 4 test case edits

similar to the 'Results' tab.

this module in two such that the configuration of the test case
packaging tool is separate from the implementation.

Seems I accidentally checked in 10.4.2-2-c-1.js.orig in addition to 10.4.2-2-c-1.js.  Removed 10.4.2-2-c-1.js.orig.

- fixed issues in 10.6-13-a-1.js, 13.2-17-1.js, and 15.5.4.20-2-46.js.  Still have a number
  of test bugs to look into once I get more free time though