- 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'
-
- Aug 11, 2015
-
-
André Bargull authored
-
- Aug 06, 2015
-
-
André Bargull authored
-
- Jul 17, 2015
-
-
André Bargull authored
-
- Jun 18, 2015
-
-
Mike Pennisi authored
Some tests specifically concern the application of the `use strict` directive as it appears in JavaScript source code. These tests should *not* be run with the `onlyStrict` flag because relying on the test runner to enable strict mode makes the semantics of the source code irrelevant. Update these tests to use the `noStrict` flag. Other tests concern language semantics that are only valid in strict mode, but the mechanism for enabling strictness is inconseqential. Update these tests to use the `onlyStrict` flag and remove any redundant `use strict` directive prologues contained within. Still other tests are valid both within and outside of strict mode. In keeping with the majority of other tests, do not specify any restrictions on the environments in which these tests may be run.
-
- Dec 07, 2014
-
-
Brian Terlson authored
-