Google Git
Sign in
chromium / external / github.com / tc39 / test262 / 9875641a4c8610729a83eebf07416d77315f216c
commit9875641a4c8610729a83eebf07416d77315f216c[log] [tgz]
authorJosh Wolfe <thejoshwolfe@gmail.com>Wed Aug 23 18:34:25 2017
committerLeo Balter <leonardo.balter@gmail.com>Wed Aug 23 18:34:25 2017
tree01e7796b9f6c555051daa080b2dbeee0bafa47dd
parentd91044c788b3ccd5efee20af70b385ad9ff1e24a [diff]
Add BigInt into the known features list (#1195)
1 file changed
tree: 01e7796b9f6c555051daa080b2dbeee0bafa47dd
  1. docs/
  2. harness/
  3. src/
  4. test/
  5. tools/
  6. website/
  7. .editorconfig
  8. .gitattributes
  9. .gitignore
  10. .hgignore
  11. .jshintrc
  12. .npmrc
  13. .travis.yml
  14. CONTRIBUTING.md
  15. ECMA TR-104.pdf
  16. excludelist.xml
  17. features.txt
  18. github-deploy-key.enc
  19. INTERPRETING.md
  20. LICENSE
  21. lint.whitelist
  22. make.py
  23. README.md
README.md

Test262 is the official ECMAScript (ECMA-262) conformance suite.

Test262 tests conformance to the continually maintained draft future ECMAScript standard found at http://tc39.github.io/ecma262/ , together with any Stage 3 or later TC39 proposals. It is maintained by Tom Care (@tcare) and Leo Balter (@leobalter) with significant contributions from many in the ECMAScript community.

This project is also described by the Ecma Technical Report 104.

Contributing to Test262

See CONTRIBUTING.md

  1. Sign the Test262 CLA.
  2. Send a pull request. Please make sure you have one commit per pull request. If you have multiple commits, squash them before sending the pull request.

Running Test262

See INTERPRETING.md

There are a number of volunteer-maintained projects that may be used to execute Test262 in various ECMAScript hosts: