summaryrefslogtreecommitdiff
path: root/test/built-ins/Array/prototype/reduceRight
Commit message (Collapse)AuthorAgeFilesLines
* js-beautify: make all indentation consistent (depth & character) (#1409)Rick Waldron2018-02-09250-3001/+3444
|
* Frontmatter: fixup "info: >" to "info: |"Rick Waldron2018-01-051-1/+1
|
* add esid to array/prototype/reduceRight tests (#1118)Sue Lockwood2017-06-30251-36/+287
|
* Remove unnecessary testsLeo Balter2017-05-173-75/+0
| | | | | | | | | These tests are not adding any coverage to the respective API they should be covering. There are other files checking cases for array-like objects, and playing this with the global might cause issues and unnexpected behavior on specific environments like browsers.
* Merge pull request #963 from leobalter/prop-descsRick Waldron2017-04-284-20/+49
|\ | | | | Cleanup prop desc tests in the Array folder
| * Add and update common tests for Array and Array.prototypeLeo Balter2017-04-114-20/+49
| | | | | | | | Ref #960
* | Remove execute bit from files (#976)André Bargull2017-04-131-0/+0
|/
* Remove unused variablesLeonardo Balter2016-06-213-3/+0
| | | | Fixes gh-597
* Reduce reliance on `fnGlobalObject.js`Mike Pennisi2016-04-254-25/+23
| | | | | | | | | | 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).
* Add missing tests for "length" and "name" properties of built-in functionsAndré Bargull2016-01-151-0/+26
| | | | Note: Already uses the updated DataView function lengths from tc39/ecma262#266 (ES2016 Draft 2015-12-20)
* Merge pull request #415 from anba/remove-runTestCase-finallyRick Waldron2015-09-0443-456/+75
|\ | | | | Replace runTestCase when used with try-finally
| * Replace runTestCase with assert, try-finally, [test/built-ins/Array]André Bargull2015-08-1343-456/+75
| |
* | Replace runTestCase with assert helpers, rest [test/built-ins]André Bargull2015-08-1311-114/+37
| |
* | Replace runTestCase with assert helpers [test/built-ins]André Bargull2015-08-1313-106/+16
|/
* Replace runTestCase with assert.throws [test/built-ins/Array]André Bargull2015-08-1131-352/+86
|
* Replace runTestCase with assert helpers ↵André Bargull2015-08-06157-965/+324
| | | | [test/built-ins/Array/prototype/reduceRight]
* Remove links to hg.ecmascript.orgAndré Bargull2015-07-17255-1020/+255
|
* Update handling of directive prologuesMike Pennisi2015-06-181-1/+1
| | | | | | | | | | | | | | | | | 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.
* Fix strict mode errors in built-ins/ArrayAndré Bargull2015-04-292-0/+2
| | | | | | | | | - Add missing "var" declarations and noStrict flags - Move code which requires non-strict semantics from Array.prototype.find_this-arg.js to Array.prototype.find_this-arg-receiver-primitive.js - Remove duplicate code from Array.prototype.findIndex_this-arg.js, already present in Array.prototype.findIndex_this-arg-receiver-primitive.js - Remove test code from Array.of_assignment-to-new-object-length.js, does not work in strict mode Part of issue #35
* Reorganize ./testBrian Terlson2014-12-07255-0/+8873