Official ECMAScript Conformance Test Suite
Go to file
Kevin Gibbons c1d09be840 add more cases for float16 coercions 2024-03-25 15:22:57 -07:00
.circleci CI: Move from deprecated to supported Docker image 2023-10-19 08:44:55 -07:00
.github/workflows Append newline and use working_directory 2022-11-28 16:37:08 -08:00
docs Correct typos 2023-02-15 09:04:26 -08:00
harness add more cases for float16 coercions 2024-03-25 15:22:57 -07:00
implementation-contributed Replace Object.hasOwnProperty.call with Object.prototype.hasOwnProperty.call 2022-11-30 16:04:02 -08:00
rfcs fixup: Changes based on 1st RFC experience 2023-02-15 09:21:07 -08:00
src Use import-attributes flag in new generated tests 2023-10-26 18:21:19 -07:00
test [explicit-resource-management] Add using in bytecode generator 2024-03-25 19:18:58 +01:00
tools Replace "imp" module with "importlib" in parseTestRecord 2023-11-15 09:15:47 -08:00
.editorconfig Add .case and .template files to .editorconfig 2022-02-16 09:56:59 -05:00
.gitattributes Import tests from Google V8 (templates) 2015-04-02 12:13:51 -04:00
.gitignore Atomics: fix typo "throwes" => "throws" 2018-06-26 14:51:45 -04:00
.hgignore Regenerated console runner files. Excluded generated test cases. 2012-08-26 20:47:30 -07:00
.npmrc Only apps should have lockfiles 2017-07-25 23:05:46 -07:00
CODEOWNERS Allow @tc39-staging to modify features.txt 2023-10-12 10:03:23 +02:00
CODE_OF_CONDUCT.md Add CoC.md reference file 2018-04-11 16:16:55 -04:00
CONTRIBUTING.md Remove backtick from CONTRIBUTING.md 2023-04-11 15:18:17 -07:00
ECMA TR-104.pdf Update TR-104 with released version 2017-05-18 15:47:35 -04:00
INTERPRETING.md Document staging folder 2022-11-02 10:02:12 +01:00
LICENSE Whitespace cleanups. CRLF => LF 2019-10-08 20:44:09 -04:00
README.md Fixed website section in README (#3981) 2024-01-09 10:48:12 +01:00
excludelist.xml Fix packager.py for updated locations 2014-12-09 14:52:12 -08:00
features.txt [explicit-resource-management] Add using in bytecode generator 2024-03-25 19:18:58 +01:00
github-deploy-key.enc Update deploy keys 2017-04-24 15:11:02 -04:00
lint.exceptions Fix lint.exceptions, I hope? 2020-03-02 13:38:35 -05:00
make.py Rename usage of master to main 2020-07-15 15:47:15 -04:00
package.json Bump esvu version 2022-12-01 15:16:40 +01: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 must be interpreted by a test runner is in INTERPRETING

Rationale

This project offers an explanation for many of its design decisions and maintenance practices--see rationale.md.

Test262 Runners

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

How To Read CI Results

Test262 runs CI tests against every PR and commit. The only tests that are required to pass are visibly flagged as REQUIRED. The CI test results that are attributed to specific runs against specific engines should not be perceived as meaningful to anyone but the person that is reviewing the test material contained within the contributed changeset. These tests are almost always expected to fail, especially in the case of tests for new features. They may be helpful in determining whether or not a regression occurred, but that can only be determined by an actual human reviewing the results and comparing those outcomes to the expected outcomes of the tests.

Where did website/ go?

It's been removed. If you need to access the code that contained in that directory, you can find it here.