tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
test262/README.md

45 lines
3.1 KiB
Markdown
Raw Normal View History

Fix parentheses
2017-10-12 16:38:16 +02:00
## Test262: ECMAScript Test Suite ([ECMA TR/104](http://ecma-international.org/publications/techreports/E-TR-104.htm))
Add a basic readme
2014-07-03 21:18:01 +02:00
Update README.md
2016-01-19 22:10:39 +01:00
readme revisions, first pass
2017-10-10 16:28:52 +02:00
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](https://tc39.github.io/ecma262/)
- [ECMA-402, ECMAScript Internationalization API Specification](https://tc39.github.io/ecma402/)
- [ECMA-404, The JSON Data Interchange Format](https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf) (pdf)
Test262 itself is described in [ECMA TR/104]((http://ecma-international.org/publications/techreports/E-TR-104.htm)) and is included in [ECMA-414](http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-414.pdf) (pdf).
Goals & State of Test262
2017-10-16 20:24:02 +02:00
### Goals & State of Test262
Add "fixme" and notes to README I'm leaving these todos for Leo or Rick -- I think you can explain the state and goal of Test262 better than me at this point!
2017-10-13 01:15:26 +02:00
Goals & State of Test262
2017-10-16 20:24:02 +02:00
The goal of Test262 is to provide test material that covers every observable behavior specified in the [ECMA-414 Standards Suite](http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-414.pdf). 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](http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-414.pdf). 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.
Add "fixme" and notes to README I'm leaving these todos for Leo or Rick -- I think you can explain the state and goal of Test262 better than me at this point!
2017-10-13 01:15:26 +02:00
### ECMAScript feature proposals
readme revisions, first pass
2017-10-10 16:28:52 +02:00
As defined in the [TC39 Process](https://tc39.github.io/process-document/), 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.
Add link in the README file
2017-05-18 21:53:41 +02:00
Added contributing.md and improved README
2014-07-04 02:13:42 +02:00
### Contributing to Test262
Add a basic readme
2014-07-03 21:18:01 +02:00
readme revisions, first pass
2017-10-10 16:28:52 +02:00
Guidance for contributing to Test262 can be found in [CONTRIBUTING.md](./CONTRIBUTING.md).
**Authors of contributions from non-Ecma member organizations must sign the [Test262 CLA](http://tc39.github.io/test262-cla)**
Add documentation on interpreting tests (#508) The project's CONTRIBUTING.md was written with test authors in mind. It contains details on non-technical metadata (e.g. "author" and "es6id"), helper function usage, and preferred code structure. In addition, it elides certain low-level technical details on the requirements for the runtime environment. Introduce a new document targeted towards those executing the tests. Formalize all expectations regarding how the runtime environment should be defined, how metadata should be interpreted, and how results should be understood. This information has overlap with the CONTRIBUTING.md file, but it also contains details that are irrelevant to test authors. This document can serve as a more formal contract between Test262 and the implementors who consume it. This allows Test262 to unambiguously document future modifications to the formal requirements which in turn supports consumers who maintain their own test harnesses.
2016-04-18 20:31:51 +02:00
### Running Test262
readme revisions, first pass
2017-10-10 16:28:52 +02:00
Guidance for running Test262 and explanations of how a test file is interpreted by a test runner is in [INTERPRETING](./INTERPRETING.md)
### Test262 Runners & Harnesses
Add links to volunteer-maintained test runners
2016-07-07 04:48:10 +02:00
readme revisions, first pass
2017-10-10 16:28:52 +02:00
Volunteer-maintained projects that may be used to execute Test262 in various ECMAScript hosts:
Add links to volunteer-maintained test runners
2016-07-07 04:48:10 +02:00
- https://github.com/bterlson/test262-harness (platform: Node.js)
- https://github.com/test262-utils/test262-harness-py (platform: Python)
Add link to web-based runner (#801)
2016-11-29 20:35:01 +01:00
- https://bakkot.github.io/test262-web-runner/ (platform: web)