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
1,268 Commits 17 Branches 0 Tags 144 MiB
JavaScript 99.7%
Python 0.2%
Go to file
Leonardo Balter d9a277aa7c Fix location based return value for Date on subclassing tests 
Fixes #489
 		2016-02-22 13:53:43 -05:00
docs Rename `String.prototype.contains` to `String.prototype.includes` 2014-12-10 13:27:42 -08:00
harness Last minute fixes 2016-02-19 11:27:31 -08:00
test Fix location based return value for Date on subclassing tests 2016-02-22 13:53:43 -05:00
tools Runner: Re-use lock to share access to stdout 2016-02-10 17:15:49 -05:00
website Remove links to hg.ecmascript.org (non-license content) 2015-07-17 17:43:27 +02:00
.gitattributes Import tests from Google V8 (templates) 2015-04-02 12:13:51 -04:00
.gitignore async,promises: initial tests of Promises 2014-07-18 05:37:08 +01: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
CONSOLE-RUNNER.md Enable parallel test execution in console runner 2016-02-08 17:40:16 +01:00
CONTRIBUTING.md s/id/esid 2016-02-22 09:47:42 -05:00
LICENSE New tests and test fixes for ECMAScript Internationalization API. 2013-03-24 23:48:59 -07:00
README.md Update README.md 2016-01-19 13:10:39 -08:00
excludelist.xml Fix packager.py for updated locations 2014-12-09 14:52:12 -08:00

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 Gorkem Yakin (@goyakin) with significant contributions from many in the ECMAScript community.

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.