tyler.durden/test262
1
0
Fork 0
mirror of https://github.com/tc39/test262.git synced 2025-07-23 22:15:24 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix generate test explination

Browse Source
This commit is contained in:
Valerie R Young 2017-10-17 12:57:44 -04:00
parent b93f7a88cd
commit 6c41ddde40
1 changed files with 17 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
CONTRIBUTING.md
View File

@ -295,18 +295,23 @@ Some language features are expressed through a number of distinct syntactic form
Test cases and test templates specify meta-data using the same YAML frontmatter pattern as so-called "static" (i.e. non-generated) tests. The expected attributes differ between test cases and test templates: Test cases and test templates specify meta-data using the same YAML frontmatter pattern as so-called "static" (i.e. non-generated) tests. The expected attributes differ between test cases and test templates:
- test cases (`*.case`) ### test cases (`*.case`)
- `template` - name of the sub-directory to locate templates for this test Field | Description
- `description` (see above) ------|-------------
// looks like this is actually "desc" !!! add how its made description with the appending of "name" in parens from the test template `template` | name of the sub-directory to locate templates for this test
- `info` (see above) `desc` | see the frontmatter definition of the "desc" field. The generated test will have a have final "desc" value which is this text appended with the test template's "name" field in parentheses.
- `features` (see above; merged with value defined by test template) `info` | see the frontmatter definition of the "info" field. The generated test will have a have final "info" value which is this text appended with the test template's "info" text.
- test templates (`*.template`) `features` | see the frontmatter definition of the "features" field. The generated test will have a final feature list in combination with the template's feature field.
- `path` - location within the published test hierarchy to output files created from this template
- `name` - human-readable name of the syntactic form described by this template (used to generate the test file's `description` field) ### test templates (`*.template`)
- `esid` (see above) Field | Description
- `info` (see above) ------|-------------
- `features` (see above; merged with value defined by test case) `path` | location within the published test hierarchy to output files created from this template. This path will be ended with the name of the test case file. If path is "/test/language/template1-" and the test case is "cast1.js", the final location of the file will be "/test/language/template1-case1.js"
`name` | human-readable name of the syntactic form described by this template. This text will be appended, in parentheses, to the end of the test cases `desc` field.
`esid` | see the frontmatter definition of the "info" tag.
`info` | see the frontmatter definition of the "info" tag. The generated test will have a have final "info" value which is this text concatenated at the end of the test case's "info" text.
`features` | see the frontmatter definition of the "features" field. The generated test will have a final feature list in combination with the test case's feature field.
any other valid frontmatter field | see the frontmatter definitions.
Generated files are managed using the `make.py` Python script located in the root of this repository. Generated files are managed using the `make.py` Python script located in the root of this repository.