Official ECMAScript Conformance Test Suite
Go to file
Frank Yung-Fong Tang 642929b2a3 correct value that matches languageAlias in
Per  https://tc39.github.io/ecma402/#sec-canonicalizelanguagetag
6.2.3 CanonicalizeLanguageTag ( locale )
The CanonicalizeLanguageTag abstract operation returns the canonical and case-regularized form of the locale argument (which must be a String value that is a structurally valid Unicode BCP 47 Locale Identifier as verified by the IsStructurallyValidLanguageTag abstract operation). A conforming implementation shall take the steps specified in the “BCP 47 Language Tag to Unicode BCP 47 Locale Identifier” algorithm, from Unicode Technical Standard #35 LDML § 3.3.1 BCP 47 Language Tag Conversion.

And
http://unicode.org/reports/tr35/#BCP_47_Language_Tag_Conversion
"
2. If the BCP 47 primary language subtag matches the type attribute of a languageAlias element in Supplemental Data, replace the language subtag with the replacement value.
If there are additional subtags in the replacement value, add them to the result, but only if there is no corresponding subtag already in the tag.
"
and
https://www.unicode.org/repos/cldr/trunk/common/supplemental/supplementalMetadata.xml
...
<languageAlias type="aar" replacement="aa" reason="overlong"/>
 <!--  [Afar]  -->
...
<languageAlias type="ces" replacement="cs" reason="overlong"/>
 <!--  [Czech]  -->
...
<languageAlias type="heb" replacement="he" reason="overlong"/>
 <!--  [Hebrew]  -->
2019-02-14 15:07:54 -05:00
docs Rename `String.prototype.contains` to `String.prototype.includes` 2014-12-10 13:27:42 -08:00
harness Introduce $262.agent.safeBroadcast and migrate Atomics tests. 2018-11-20 15:17:47 -05:00
implementation-contributed Merge pull request #2037 from test262-automation/v8-test262-automation-export-ad1b4aadf8 2019-02-04 12:04:39 -07:00
src Fixing async tests and other NIT changes 2019-02-06 18:18:48 -02:00
test correct value that matches languageAlias in 2019-02-14 15:07:54 -05:00
tools Linter should require direct throw statement for raw tests instead of DONOTEVALUATE 2019-02-14 15:06:08 -05: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 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
.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 Use travis ci to run new or modified test files on engines 2018-11-07 10:03:00 -05:00
CODE_OF_CONDUCT.md Add CoC.md reference file 2018-04-11 16:16:55 -04:00
CONTRIBUTING.md Document raw negative test reqs 2019-02-14 15:06:08 -05:00
ECMA TR-104.pdf Update TR-104 with released version 2017-05-18 15:47:35 -04:00
INTERPRETING.md Introduce $262.agent.safeBroadcast and migrate Atomics tests. 2018-11-20 15:17:47 -05:00
LICENSE New tests and test fixes for ECMAScript Internationalization API. 2013-03-24 23:48:59 -07:00
README.md Added URL for C++ test harness. (#1615) 2018-06-29 14:59:45 -04:00
excludelist.xml Fix packager.py for updated locations 2014-12-09 14:52:12 -08:00
features.txt Apply review feedback for hashbang 2019-02-14 15:06:08 -05:00
github-deploy-key.enc Update deploy keys 2017-04-24 15:11:02 -04:00
lint.exceptions rename whitelist to exceptions in the linter tool (#2004) 2018-12-18 15:39:57 -02:00
make.py Automate deployment (#546) 2017-04-10 15:31:19 -04:00
package.json Use travis ci to run new or modified test files on engines 2018-11-07 10:03:00 -05: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: