Assert the expected behavior of the ArraySpeciesCreate abstract
operation in the 5 Array instance methods from which it is invoked.
This change set does not include tests for ECMAScript realm
considerations because Test262 does not currently expose a mechanism for
interfacing with realms.
This harness function is not necessary in the majority of cases in which
it is used. Remove its usage to simplify tests and decrease the amount
of domain-specific knowledge necessary to contribute to the test suite.
Persist the harness function itself for use by future tests for ES2015
modules (such a helper is necessary for tests that are interpreted as
module code).
Because Test262 asserts the strict equality of
`Array.prototype.toString` and `TypedArray.prototype.toString`, tests
for properties of the object do not need to be reproduced in both
location.
Ref gh-526
- 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
- fixed a false positive where argument-passed-null.js was returning a TypeError from 22.1.2.1 step 5
- created 2 tests from argument-passed-null to assert this as null and items as null
- fixed reference info on Array.from_arity.js
- fix tests at Array.from_forwards-length-for-array-likes
- static checks on calling-from-valid-1-onlyStrict.js
- static checks on calling-from-valid-1-noStrict.js
- static checks on calling-from-valid-2.js
- removed create-typedarray-from.js, that test belong to es6id 22.2.2.1
- removed mapfn-invalid-typeerror-1.js - false positive from 22.1.2.1 step 5
- moved mapfn-invalid-typeerror-2.js to more spread tests where mapfn is not callable
- ...