tyler.durden
/
test262
mirror of https://github.com/tc39/test262.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Introduce version number (#1255) 

Changes to the instructions for interpreting tests will likely produce
new failures for consumers who are updating between revisions of
Test262. Introduce a machine-readable convention for signaling
substantive changes.
This commit is contained in:
jugglinmike 2017-10-02 11:12:14 -04:00 committed by Leo Balter
parent f3b5a1e4c0
commit a7f5616713
2 changed files with 20 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
INTERPRETING.md
View File

@ -4,6 +4,11 @@ All tests are declared as text files located within this project's `test`
directory. In order to execute Test262 tests, runtimes must observe the directory. In order to execute Test262 tests, runtimes must observe the
following semantics. following semantics.
**Note** When these instructions change in any substantive way, the `version`
property of the JSON-formatted `package.json` file will be incremented. In this
way, consumers who are transitioning between revisions of Test262 can more
easily determine the cause of new test failures.
## Test Execution ## Test Execution
Test262 tests are only valid under the runtime environment conditions described Test262 tests are only valid under the runtime environment conditions described

15
package.json Normal file
View File

@ -0,0 +1,15 @@
{
"name": "test262",
"version": "1.0.0",
"description": "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.",
"repository": {
"type": "git",
"url": "git+https://github.com/tc39/test262.git"
},
"license": "BSD",
"bugs": {
"url": "https://github.com/tc39/test262/issues"
},
"private": true,
"homepage": "https://github.com/tc39/test262#readme"
}