4 Commits

Author	SHA1	Message	Date
Adrian Heine	21f6a86a6d	Remove explicit sta.js includes ... INTERPRETING.md states that sta.js has to be included unconditionally.	2018-10-15 12:45:55 -04:00
Rick Waldron	1a2244faf8	Fix all test/harness/*.js tests (#1068) ... $ test262-harness --hostType=d8 -t 4 --hostPath=`which d8` test/harness/*.js Ran 147 tests 147 passed 0 failed $ test262-harness --hostType=node -t 4 --hostPath=`which node` test/harness/*.js Ran 147 tests 147 passed 0 failed $ test262-harness --hostType=jsshell -t 4 --hostPath=`which js` test/harness/*.js Ran 147 tests 147 passed 0 failed Signed-off-by: Rick Waldron <waldron.rick@gmail.com>	2017-06-22 22:25:35 -03:00
Mike Pennisi	29ecced632	Update handling of directive prologues ... 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.	2015-06-18 17:38:34 -04:00
Mike Pennisi	3211e33199	Add tests for test harness	2015-04-22 18:38:40 -04:00