tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Official ECMAScript Conformance Test Suite
2,847 Commits 18 Branches 0 Tags 141 MiB
JavaScript 99.7%
Python 0.2%
Go to file
Mike Pennisi 90c667afd1 fixup! Add tests for parsing behavior 2018-06-17 20:36:55 -04:00
docs Rename `String.prototype.contains` to `String.prototype.includes` 2014-12-10 13:27:42 -08:00
harness Merge pull request #1560 from tc39/intl-update-iana-subtags-2018-04-23 2018-06-04 16:22:01 -04:00
implementation-contributed/javascriptcore Implementation Contributions: Creating initial empty dir for receiving "upstreamed" test material via automaton 2018-05-29 13:50:10 -04:00
src Add templated tests for new proposed Annex B semantics 2018-05-11 15:48:43 -04:00
test fixup! Add tests for parsing behavior 2018-06-17 20:36:55 -04:00
tools Lint: disallow calls to verifyConfigurable and verifyProperty in same file 2018-06-07 22:38:36 -04:00
website fix: comparing typeof expression 2018-05-31 23:27:46 +08:00
.editorconfig Unify indentation and add .editorconfig (#973) 2017-04-13 10:37:32 -04:00
.gitattributes Import tests from Google V8 (templates) 2015-04-02 12:13:51 -04:00
.gitignore Only apps should have lockfiles 2017-07-25 23:05:46 -07:00
.hgignore Regenerated console runner files. Excluded generated test cases. 2012-08-26 20:47:30 -07:00
.jshintrc Added new tests for chapters 6 and 9 of ECMAScript Internationalization API Specification. 2012-08-26 20:49:25 -07:00
.npmrc Only apps should have lockfiles 2017-07-25 23:05:46 -07:00
.travis.yml Install linter dependencies in CI 2017-12-02 23:05:23 -05:00
CODE_OF_CONDUCT.md Add CoC.md reference file 2018-04-11 16:16:55 -04:00
CONTRIBUTING.md Update filename character restriction in documention, linter and a few filenames 2018-05-11 22:19:01 -04:00
ECMA TR-104.pdf Update TR-104 with released version 2017-05-18 15:47:35 -04:00
INTERPRETING.md Formalize asynchronous failure conditions 2018-05-20 15:24:55 -04:00
LICENSE New tests and test fixes for ECMAScript Internationalization API. 2013-03-24 23:48:59 -07:00
README.md Goals & State of Test262 2017-10-16 14:24:02 -04:00
excludelist.xml Fix packager.py for updated locations 2014-12-09 14:52:12 -08:00
features.txt Add tests for Symbol.prototype.description 2018-06-07 21:39:02 +08:00
github-deploy-key.enc Update deploy keys 2017-04-24 15:11:02 -04:00
lint.whitelist Remove faulty `throw` statements 2017-07-13 12:27:29 -04:00
make.py Automate deployment (#546) 2017-04-10 15:31:19 -04:00
package.json v3.0.0 2018-05-03 13:28:46 -04:00

README.md

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 CONTRIBUTING.md.

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: