- Jan 29, 2016
-
-
Leonardo Balter authored
Fixes gh-482
-
- Jan 15, 2016
-
-
André Bargull authored
Note: Already uses the updated DataView function lengths from tc39/ecma262#266 (ES2016 Draft 2015-12-20)
-
- Dec 15, 2015
-
-
Jordan Harband authored
-
- Sep 07, 2015
-
-
André Bargull authored
- String case functions iterate over code points - Has called before Get in Array.p.reverse - Add test for web-compat Array.p.splice behaviour; Plus missing test for no arguments case - ToObject no longer applied to this-value in Array.p.toLocaleString - ToObject no longer applied to this-value in Object.p.toLocaleString - Add tests for Object.p.propertyIsEnumerable and symbol property keys - Add tests for Object.p.hasOwnProperty and symbol property keys - Test property descriptor attributes of message property - Tests for RegExp constructor checks - Date constructor when called with date object - TimeClip never returns negative zero
-
- Aug 13, 2015
-
-
André Bargull authored
-
André Bargull authored
-
- Aug 11, 2015
-
-
André Bargull authored
-
André Bargull authored
-
André Bargull authored
-
André Bargull authored
-
André Bargull authored
-
André Bargull authored
-
André Bargull authored
-
André Bargull authored
-
André Bargull authored
-
- Aug 08, 2015
-
-
Mike Pennisi authored
-
- Jul 17, 2015
-
-
André Bargull authored
- Remove duplicate word - Add missing license
-
André Bargull authored
-
- Jul 10, 2015
-
-
Mike Pennisi authored
The `negative` frontmatter tag expresses an expectation for the behavior of the test file as a whole. The `assert.throws` helper function offers more fine-grained control over expectations because it may be applied to specific statements and expressions. This makes it preferable in cases where it may be used (i.e. when the test body does not describe a syntax error or early error). Re-implement assertions for errors to use the `assert.throws` helper function wherever possible.
-
- Jul 06, 2015
-
-
Leonardo Balter authored
- move Object.prototype.__proto__ tests to annexB - remove RegExp.prototype.unicode name test
-
Leonardo Balter authored
Including: - 21.2.4.2 get RegExp [ @@species ] - 21.2.5.3 get RegExp.prototype.flags - 21.2.5.4 get RegExp.prototype.global - 21.2.5.5 get RegExp.prototype.ignoreCase - 21.2.5.7 get RegExp.prototype.multiline - 21.2.5.10 get RegExp.prototype.source - 21.2.5.12 get RegExp.prototype.sticky - 21.2.5.15 get RegExp.prototype.unicode - 22.1.2.5 get Array [ @@species ] - 23.1.2.2 get Map [ @@species ] - 23.2.2.2 get Set [ @@species ] - 24.1.3.3 get ArrayBuffer [ @@species ] - 24.1.4.1 get ArrayBuffer.prototype.byteLength - 24.2.4.1 get DataView.prototype.buffer - 24.2.4.2 get DataView.prototype.byteLength - 24.2.4.3 get DataView.prototype.byteOffset - 25.4.4.6 get Promise [ @@species ] - B.2.2.1.1 get Object.prototype.__proto__ - B.2.2.1.2 set Object.prototype.__proto__ Skipped TypedArray tests in order to avoid an early test strategy definition for them.
-
- Jun 28, 2015
-
-
Pieter van Ginkel authored
Two tests started the configuration block with a /*-- instead of a /*---.
-
- Jun 19, 2015
-
-
Mike Pennisi authored
-
Mike Pennisi 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.
-
Yanli Xu authored
-
- Jun 16, 2015
-
-
Mike Pennisi authored
The `$PRINT` helper function has no effect on test behavior. The following tests use it to report assertion outcomes (and as a result will fail silently): - test/language/function-code/S10.2.1_A4_T2.js - test/language/function-code/S10.2.1_A5.1_T1.js - test/language/function-code/S10.2.1_A5.1_T2.js - test/language/function-code/S10.2.1_A5.2_T1.js Remove the function definition and all references within tests. Update tests that use it as an error reporting mechanism to instead use an appropriate `assert` helper function.
-
Mike Pennisi authored
In neglecting to assert the type of error thrown (or that any error was thrown at all), these tests cannot fail. Refactor the tests to use the `assert.throws` helper method, which takes these details into consideration.
-
- Jun 09, 2015
-
-
Mike Pennisi authored
This function is equivalent to `$ERROR` (which is automatically included in test environments). Remove the harness file that defines the function, remove references to the file from test `includes` lists, and update scripts to instead invoke the `$ERROR` function.
-
- May 18, 2015
-
-
André Bargull authored
- Remove no longer needed noStrict flags. - Change tests to use propertyHelper.js for strict mode compatibility. - Add tests for return value of `delete` operator, e.g. `delete Array.prototype === false`. - Add non-writable tests for global NaN property. - Split some tests to run in strict mode. - Change tests with global `var length` declaration to use a different variable name for browser environments. - Merge duplicated tests symbol-data-property-configurable-non-strict and symbol-data-property-configurable-strict. - Merge duplicated tests symbol-data-property-writable-non-strict and symbol-data-property-writable-strict. - (And a small change in propertyHelper to reduce code duplication in function call.)
-
- May 07, 2015
- May 06, 2015
-
-
smikes authored
-
- May 03, 2015
-
-
smikes authored
-
- May 02, 2015
-
-
smikes authored
-
- Apr 29, 2015
-
-
André Bargull authored
- Add missing "var" declarations and noStrict flags - Remove invalid noStrict flags - ietestcenter tests need fixed, require updates to use propertyHelper.js Part of issue #35.
-
- Apr 27, 2015
-
-
André Bargull authored
- in-statement-position-label-statement.js is an Annex-B test (B.3.2 Labelled Function Declarations), moved to annexB directory - identifier-let-allowed-as-lefthandside-expression-strict.js needs to check for a SyntaxError (ES6, 12.1.1) - Remove sort() calls in test/built-ins/Object/getOwnPropertyNames/*.js - Remove sort() calls in test/language/block-scope/syntax/for-in/acquire-properties-from-*.js - verifyConfigurable() needs to called last in test/built-ins/Object/is/length.js - All productions within ClassBody are implicitly strict, update test/language/class/method-definition/yield-as-*.js accordingly - Remove unnecessary noStrict flag in test/language/class/method-definition/yield-as-generator-method-binding-identifier.js - Check own symbols are returned in property creation order from Object.getOwnPropertySymbols(): - test/language/computed-property-names/basics/symbol.js - test/language/computed-property-names/class/method/symbol.js - test/language/computed-property-names/class/static/method-symbol.js - test/language/computed-property-names/object/method/symbol.js - Fix copy-paste error in test/language/expressions/object/method-definition/yield-as-function-expression-binding-identifier.js
-
- Apr 21, 2015
-
-
Rick Waldron authored
7.2.9 SameValue(x, y)
-