Official ECMAScript Conformance Test Suite
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs Rename `String.prototype.contains` to `String.prototype.includes` Dec 10, 2014
harness Introduce $262.agent.safeBroadcast and migrate Atomics tests. Nov 20, 2018
implementation-contributed Merge pull request #2037 from test262-automation/v8-test262-automatio… Feb 4, 2019
src Adding destructuring-binding on feature list Feb 14, 2019
test Remove unreasonable expectation Feb 14, 2019
tools Linter should require direct throw statement for raw tests instead of… Feb 14, 2019
website fix: comparing typeof expression May 31, 2018
.editorconfig Unify indentation and add .editorconfig (#973) Apr 13, 2017
.gitattributes Import tests from Google V8 (templates) Apr 2, 2015
.gitignore Atomics: fix typo "throwes" => "throws" Jun 26, 2018
.hgignore Regenerated console runner files. Excluded generated test cases. Aug 27, 2012
.jshintrc Added new tests for chapters 6 and 9 of ECMAScript Internationalizati… Aug 27, 2012
.npmrc Only apps should have lockfiles Jul 26, 2017
.travis.yml Use travis ci to run new or modified test files on engines Nov 7, 2018 Add reference file Apr 11, 2018 Document raw negative test reqs Feb 14, 2019
ECMA TR-104.pdf Update TR-104 with released version May 18, 2017 Introduce $262.agent.safeBroadcast and migrate Atomics tests. Nov 20, 2018
LICENSE New tests and test fixes for ECMAScript Internationalization API. Mar 25, 2013 Added URL for C++ test harness. (#1615) Jun 29, 2018
excludelist.xml Fix for updated locations Dec 9, 2014
features.txt Apply review feedback for hashbang Feb 14, 2019
github-deploy-key.enc Update deploy keys Apr 24, 2017
lint.exceptions rename whitelist to exceptions in the linter tool (#2004) Dec 18, 2018 Automate deployment (#546) Apr 10, 2017
package.json Use travis ci to run new or modified test files on engines Nov 7, 2018

Test262: ECMAScript Test Suite (ECMA TR/104)

Test262 is the implementation conformance test suite for the latest drafts (or most recent published edition) of the following Ecma specifications:

Test262 itself is described in ECMA TR/104 and is included in ECMA-414 (pdf).

Goals & State of Test262

The goal of Test262 is to provide test material that covers every observable behavior specified in the ECMA-414 Standards Suite. Development of Test262 is an on-going process. As of October 2017, Test262 consisted of over 29272 individual test files covering the majority of the pseudo-code algorithms and grammar productions defined in the ECMA-414 Standards Suite. Each of these files contains one or more distinct test cases. This marks the most comprehensive ECMAScript test suite to date. While test coverage is broad, TC39 does not consider coverage to be complete and as with any software project there exists the possibility of omissions and errors. This project welcomes any contributions to Test262 that help make test coverage of existing features more comprehensive.

ECMAScript feature proposals

As defined in the TC39 Process, Stage 4 Entrance Criteria requires tests for new feature proposals to advance. Tests may be written by proposal champions, implementers, or any interested community member.

A proposal champion is someone that worked on the feature proposal and specification directly.

An implementer is someone that works on implementing the proposal into a JavaScript engine, parser, runtime or embedding.

A community member is you, and we welcome you to contribute! If you're having trouble getting started, or even just want to ask a question, feel free to open an issue.

Contributing to Test262

Guidance for contributing to Test262 can be found in

Authors of contributions from non-Ecma member organizations must sign the Test262 CLA

Running Test262

Guidance for running Test262 and explanations of how a test file is interpreted by a test runner is in INTERPRETING

Test262 Runners & Harnesses

Volunteer-maintained projects that may be used to execute Test262 in various ECMAScript hosts: