- Jun 28, 2018
-
-
Valerie Young authored
-
- Jan 05, 2018
-
-
Mike Pennisi authored
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.
-
- Jun 28, 2017
-
-
Mike Pennisi authored
This pattern makes expectations more explicit by making test files more literal.
-
- Oct 19, 2016
-
-
Mike Pennisi authored
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'
-
- Mar 29, 2016
-
-
Mike Pennisi authored
Assert that relevant early errors are reported following the parsing of module code.
-
Mike Pennisi authored
-
- Jul 17, 2015
-
-
André Bargull authored
- Remove duplicate word - Add missing license
-
- Jun 03, 2015
-
-
Mike Pennisi authored
Introduce the `module` flag to unambiguously identify tests that are intended to be interpreted as module code.
-