- Feb 15, 2018
-
-
Robin Templeton authored
- add @jakobkummerow's changes - remove EOL whitespace - use 'Array.isArray' instead of 'instanceof Array' - check for BigInt type in toLocaleString tests - specify TypedArray constructor list for non-BigInt tests - update TypedArray harness test for BigInt - add a missing type coercion - disable more tests for Big(U)Int64Array - check for BigInt before using BigInt TypedArray constructors
-
- Jan 05, 2018
-
-
Rick Waldron authored
-
- Dec 21, 2017
-
-
Rick Waldron authored
-
André Bargull authored
-
André Bargull authored
-
- Sep 11, 2017
-
-
Leo Balter authored
-
- Sep 07, 2017
-
-
Leo Balter authored
-
- Jul 14, 2017
-
-
Rick Waldron authored
``` $ python tools/lint/lint.py --whitelist lint.whitelist harness/*.js Linting 25 files. Linting complete. 0 errors found. ``` - Renames detachArrayBuffer-$262.detachArrayBuffer.js -> detachArrayBuffer-host-detachArrayBuffer.js (previous naming prevents command-click from terminal) Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
- Jun 28, 2017
-
-
Rick Waldron authored
- correction to license - use Number.isNaN Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
- Jun 23, 2017
-
-
Rick Waldron authored
Signed-off-by:
Rick Waldron <waldron.rick@gmail.com>
-
Rick Waldron authored
$ 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>
-
- May 01, 2017
-
-
Leo Balter authored
-
- Apr 15, 2017
-
-
Leo Balter authored
-
- May 25, 2016
-
-
Leonardo Balter authored
Update testTypedArrayConversions to require byteConversionValues
-
- Apr 21, 2016
-
-
jugglinmike authored
Modify the regular expression for native functions' toString value to satisfy all test cases. Correct the test file's reference to the harness file. Re-format the test file's assertions to aid debugging in the event of failure.
-
- Apr 19, 2016
-
-
jugglinmike authored
The millisecond representation of a given Date instance is dependent on the local system's time zone settings. In order to pass consistently across contexts, tests for this value must take the system configuration into account. Introduce a test harness utility function to encapsulate these concerns. Re-use this function across all test files that assert the exact millisecond representation of Date instances.
-
- Apr 15, 2016
-
-
Leonardo Balter authored
-
- Apr 11, 2016
-
-
Michael Ficarra authored
See the proposal at https://tc39.github.io/Function-prototype-toString-revision/
-
- Mar 15, 2016
-
-
Leonardo Balter authored
-
- Feb 22, 2016
-
-
Leonardo Balter authored
Fixes #477
-
- Feb 19, 2016
-
-
Jordan Harband authored
-
- Feb 17, 2016
-
- Feb 13, 2016
-
-
Jordan Harband 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.
-
- Apr 22, 2015
-
-
Mike Pennisi authored
-
- Dec 09, 2014
-
-
Brian Terlson authored
-