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,477 Commits 18 Branches 0 Tags 141 MiB
JavaScript 99.7%
Python 0.2%
Go to file
Daniel Ehrenberg cb84893f93 Add a test that BigInt does not have a parseInt function 2017-12-21 15:16:22 -05:00
docs
…
harness Remove unnecessary uses of let in harness. 2017-12-19 15:50:19 -05:00
src Add features for class public fields 2017-11-28 12:46:58 -05:00
test Add a test that BigInt does not have a parseInt function 2017-12-21 15:16:22 -05:00
tools tools/lint: install PyYAML if not available. Fixes gh-1286 2017-10-18 12:21:36 -04:00
website
…
.editorconfig
…
.gitattributes
…
.gitignore Only apps should have lockfiles 2017-07-25 23:05:46 -07:00
.hgignore
…
.jshintrc
…
.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
CONTRIBUTING.md Merge pull request #1374 from jugglinmike/contributing-typo 2017-12-19 15:44:18 -05:00
ECMA TR-104.pdf
…
INTERPRETING.md Modify $262.uncallableAndIsHTMLDDA() to $262.IsHTMLDDA (#1305) 2017-10-19 15:03:21 -04:00
LICENSE
…
README.md Goals & State of Test262 2017-10-16 14:24:02 -04:00
excludelist.xml
…
features.txt Update class-fields tags in the features list 2017-11-28 12:48:02 -05:00
github-deploy-key.enc
…
lint.whitelist
…
make.py
…
package.json Introduce version number (#1255) 2017-10-02 11:12:14 -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: