d0b5137c15
* Rename & improve "length" test * Use verifyProperty in "name" test * Rename & improve property descriptor test * Remove duplicated test https://github.com/tc39/test262/blob/master/test/built-ins/Object/prototype/toString/proxy-array.js * Rename proxy value test * Rename & improve String object unwrapping test * Rename & improve Number object unwrapping test * Rename & improve Boolean object unwrapping test * Rename & merge replacer returns undefined tests * Rename & merge replacer function tests * Rename replacer array revoked proxy test * Add cross-realm replacer array revoked proxy test * Add array proxy replacer test * Add replacer array keys order test * Add empty replacer array test * Add non-finite numbers serialization test * Add replacer array abrupt completion test * Add replacer array with duplicates test * Add replacer array ignores undefined test * Add replacer array unwraps strings test * Add replacer array unwraps numbers test * Rename & merge circular object tests * Add circular array test * Rename & merge top-level primitives tests * Rename string escape tests * Rename BigInt tests * Rename & improve function value test * Add replacer function abrupt test * Rename & merge wrong space type tests * Rename float number space test * Rename & improve Number object space test * Rename & improve String object space test * Rename basic numeric space test * Rename string space slice test * Add replacer array numbers test * Add toJSON abrupt completions test * Add not callable toJSON test * Add toJSON call arguments test * Add replacer array wrong types test * Rename & improve string space test * Rename & improve replacer wrong type test * Add built-in object requirements test * Add basic toJSON result test * Add abrupt array value test * Add abrupt object value test * Rename & merge space number clamp tests * Add replacer function wrapper test * Add symbol value test * Add negative zero value test * Add replacer function & toJSON test * Add circular object from toJSON test * Add circular array from toJSON test * Add circular object from replacer test * Add circular array from replacer test * Add replacer function arguments test * Split & improve proxy value test * Split & improve revoked proxy value test |
||
|---|---|---|
| .circleci | ||
| docs | ||
| harness | ||
| implementation-contributed | ||
| src | ||
| test | ||
| tools | ||
| website | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .hgignore | ||
| .jshintrc | ||
| .npmrc | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| ECMA TR-104.pdf | ||
| INTERPRETING.md | ||
| LICENSE | ||
| README.md | ||
| excludelist.xml | ||
| features.txt | ||
| github-deploy-key.enc | ||
| lint.exceptions | ||
| make.py | ||
| package.json | ||
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:
- ECMA-262, ECMAScript Language Specification
- ECMA-402, ECMAScript Internationalization API Specification
- ECMA-404, The JSON Data Interchange Format (pdf)
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:
- https://github.com/bterlson/test262-harness (platform: Node.js)
- https://github.com/test262-utils/test262-harness-py (platform: Python)
- https://bakkot.github.io/test262-web-runner/ (platform: web)
- https://github.com/Izhido/test262_harness_cpp (platform: C++)