4 Commits

Author	SHA1	Message	Date
Mike Pennisi	136110378b	Rename negative test "phase" for parsing ... Early errors may result from parsing the source text of a test file, but they may also result from parsing some other source text as referenced through the ES2015 module syntax. The latter form of early error is not necessarily detectable by ECMAScript parsers, however. Because of this, the label "early" is not sufficiently precise for all Test262 consumers to correctly interpret all tests. Update the "phase" name of "early" to "parse" for all those negative tests that describe errors resulting from parsing of the file's source text directly. A forthcoming commit will update the remaining tests to use a "phase" name that is more specific to module resolution.	2018-01-05 15:17:50 -05:00
Mike Pennisi	81d00def42	Force "early error" tests to fail if evaluated ... This pattern makes expectations more explicit by making test files more literal.	2017-06-28 11:24:36 -04:00
Mike Pennisi	7d4b1d28ae	Re-format tests for SyntaxErrors ... Authored via the following command: $ find test -type f -print0 | \ xargs -0 sed \ -i 's/^\(\s*\)negative:\s*SyntaxError\s*$/\1negative:\n\1 phase: early\n\1 type: SyntaxError/g'	2016-10-19 15:24:21 -04:00
Mike Pennisi	6646d3e94f	Re-organize class tests ... The `test/language/class/` directory contains a small subset of Test262's tests for ES2015 classes. The majority of tests for classes are organized within `test/language/statements/class/`. - Move the tests that rely on the ClassDeclaration syntactic form from `test/language/class/` to `test/language/statements/class/`. - Move the test that relies on the ClassExpression syntactic form from `test/language/class/` to `test/language/expressions/class/`.	2015-07-10 10:36:05 -04:00