diff options
| author | Valerie R Young <spectranaut@riseup.net> | 2017-10-12 19:15:26 -0400 |
|---|---|---|
| committer | Valerie R Young <spectranaut@riseup.net> | 2017-10-12 19:15:26 -0400 |
| commit | f395874edad329d29ba9431105a2f5426f5682c4 (patch) | |
| tree | 9e0b5e1cecdf698a5d52c6a0a83e3b916864cdd1 /README.md | |
| parent | d3e2689307fe2f531b4bbb4472eb59df07229d2a (diff) | |
| download | qtdeclarative-testsuites-f395874edad329d29ba9431105a2f5426f5682c4.tar.gz | |
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!
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -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. |