tyler.durden/test262
1
0
Fork 0
mirror of https://github.com/tc39/test262.git synced 2025-04-08 19:35:28 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add "fixme" and notes to README

Browse Source 
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!
This commit is contained in:
Valerie R Young 2017-10-12 19:15:26 -04:00
parent d3e2689307
commit f395874eda
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -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.