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

22 lines
1.2 KiB
Markdown
Raw Normal View History

Added contributing.md and improved README
2014-07-04 02:13:42 +02:00
## Test262 is the official ECMAScript (ECMA-262) conformance suite.
Add a basic readme
2014-07-03 21:18:01 +02:00
Add Leo to the maintainers list
2017-03-22 18:14:18 +01:00
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.
Update README.md
2016-01-19 22:10:39 +01:00
Add link in the README file
2017-05-18 21:53:41 +02:00
This project is also described by the [Ecma Technical Report 104](http://ecma-international.org/publications/techreports/E-TR-104.htm).
Added contributing.md and improved README
2014-07-04 02:13:42 +02:00
### Contributing to Test262
document `timeout` and clean up CONTRIBUTING.md - document `timeout` tag - reorder tags in frontmatter doc - minor cleanups - minor fixes - add style note - reformat flags - remove discussion of obsolete $INCLUDE - incorporate line notes from @domenic - integrate additional comments - add links back, move arg notes down - Raise outline level by one README.md - link to CONTRIBUTING
2014-08-22 17:47:18 +02:00
> See [CONTRIBUTING.md](./CONTRIBUTING.md)
Add a basic readme
2014-07-03 21:18:01 +02:00
1. Sign the [Test262 CLA](http://tc39.github.io/test262-cla).
Update README.md
2016-01-19 22:10:39 +01:00
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.
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
> See [INTERPRETING.md](./INTERPRETING.md)
Add links to volunteer-maintained test runners
2016-07-07 04:48:10 +02:00
There are a number of volunteer-maintained projects that may be used to execute Test262 in various ECMAScript hosts:
- 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)