morning. The rewrite of "function testcase()..." now puts the
assertTrue at the bottom. Preconditions, names, and ids are
removed. And the path in the file is ignored, and is instead set
accurately according to where the file is found.

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

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...

	if (!strict_mode) { throw new SyntaxError('unspecified case'); }

This doesn't work for a few reasons:
1.  'strict_mode' is undefined in the test case exeuction context. That is, the test framework
    does not force the test case into strict mode
2.  The test case code looks like:
	"use strict";
	if (!strict_mode) ...
        ...
    Note that 'strict_mode' is not set before being accessed

Really the metadata for these test cases should have a "@strict" property added to instruct the test
framework *not* to run the test if an implementation doesn't support strict mode.

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'.