From 53778cdf1faf12671817e7a2e2def2d2f1db157a Mon Sep 17 00:00:00 2001 From: Rick Waldron Date: Tue, 10 Oct 2017 10:28:52 -0400 Subject: [PATCH 1/4] readme revisions, first pass --- README.md | 32 ++++++++++++++++++++++++-------- 1 file changed, 24 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 06229022fd..7a9ae28ea0 100644 --- a/README.md +++ b/README.md @@ -1,20 +1,36 @@ -## Test262 is the official ECMAScript (ECMA-262) conformance suite. +## Test262: ECMAScript Test Suite ([ECMA TR/104]((http://ecma-international.org/publications/techreports/E-TR-104.htm))) -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](http://ecma-international.org/publications/techreports/E-TR-104.htm). +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). + +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. ### Contributing to Test262 -> See [CONTRIBUTING.md](./CONTRIBUTING.md) -1. Sign the [Test262 CLA](http://tc39.github.io/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. +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)** ### Running Test262 -> See [INTERPRETING.md](./INTERPRETING.md) +Guidance for running Test262 and explanations of how a test file is interpreted by a test runner is in [INTERPRETING](./INTERPRETING.md) -There are a number of volunteer-maintained projects that may be used to execute Test262 in various ECMAScript hosts: + +### Test262 Runners & Harnesses + +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) From d3e2689307fe2f531b4bbb4472eb59df07229d2a Mon Sep 17 00:00:00 2001 From: Rick Waldron Date: Thu, 12 Oct 2017 10:38:16 -0400 Subject: [PATCH 2/4] Fix parentheses --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7a9ae28ea0..c094daa206 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -## Test262: ECMAScript Test Suite ([ECMA TR/104]((http://ecma-international.org/publications/techreports/E-TR-104.htm))) +## Test262: ECMAScript Test Suite ([ECMA TR/104](http://ecma-international.org/publications/techreports/E-TR-104.htm)) Test262 is the implementation conformance test suite for the latest drafts (or most recent published edition) of the following Ecma specifications: From f395874edad329d29ba9431105a2f5426f5682c4 Mon Sep 17 00:00:00 2001 From: Valerie R Young Date: Thu, 12 Oct 2017 19:15:26 -0400 Subject: [PATCH 3/4] 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! --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index c094daa206..da61c46db2 100644 --- a/README.md +++ b/README.md @@ -9,6 +9,18 @@ Test262 is the implementation conformance test suite for the latest drafts (or m 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). +### State of Test262 + +(fixme) + +In this location, we should describe the present state and ideal state of Test262: +(1) goal state: every "observable" behavior identified in ECMAScript ? +(2) current state: can you summarize how comprehensive Test262 presently is ? Perhaps breakdown by each of the stanards (262, 402 and 404) + +We welcome any contributions to Test262 that help make test coverage of existing features more comprehensive. + +### ECMAScript feature proposals + 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. From b537d405ec621896c2c239cc5a622eff6f046be7 Mon Sep 17 00:00:00 2001 From: Rick Waldron Date: Mon, 16 Oct 2017 14:24:02 -0400 Subject: [PATCH 4/4] Goals & State of Test262 --- README.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index da61c46db2..44faa6be17 100644 --- a/README.md +++ b/README.md @@ -9,15 +9,10 @@ Test262 is the implementation conformance test suite for the latest drafts (or m 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). -### State of Test262 +### Goals & State of Test262 -(fixme) +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. -In this location, we should describe the present state and ideal state of Test262: -(1) goal state: every "observable" behavior identified in ECMAScript ? -(2) current state: can you summarize how comprehensive Test262 presently is ? Perhaps breakdown by each of the stanards (262, 402 and 404) - -We welcome any contributions to Test262 that help make test coverage of existing features more comprehensive. ### ECMAScript feature proposals