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

31 lines
1.5 KiB
JSON
Raw Normal View History

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.
2017-10-02 17:12:14 +02:00
{
"name": "test262",
Update project structure to support non-JS files This change is in service of forthcoming tests for the "JSON modules" language proposal [1]. Verifying the semantics of that proposal requires modules whose source text is not valid ECMAScript; this change updates the guidelines for contributing and interpreting tests so that such test material can be handled consistently. Differentiating JSON files with a distinct file name suffice will assist consumers which require special handling of such files (e.g. web browsers). Change the pattern used to designate "fixture" files so that it may be applied to files used for JSON modules. Increment the project version number to alert consumers of this change in interpreting instructions. [1] https://github.com/tc39/proposal-json-modules
2021-05-29 00:53:04 +02:00
"version": "5.0.0",
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.
2017-10-02 17:12:14 +02:00
"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,
Use travis ci to run new or modified test files on engines
2018-11-06 21:34:53 +01:00
"homepage": "https://github.com/tc39/test262#readme",
"devDependencies": {
CI: Bump esvu to 1.2.9 1.2.8 does not install graaljs correctly.
2022-08-01 19:29:40 +02:00
"esvu": "^1.2.9",
CI: Do not report test failures as errors Prior to this patch, the CircleCI continuous integration environment was configured to report test failures in a negative light, displaying red cross-marks and reporting that "some checks were not successful" in commits and GitHub Pull Requests which included them. The passing/failing status of tests does not influence their desirability for Test262. (In practice, engines very commonly fail newly-contributed tests.) Although these conflicting interpretations does not technically interfere with the maintainers' ability to merge new contributions, it does create confusion for many contributors who interpreted the UI as a rejection of their work. In addition, this behavior made it impossible to distinguish between the benign test failures and disruptive infrastructural problems (e.g. the crashing of engines). Reconfigure the continuous integration environment to accept passing and failing tests equally, and to only report a problem when the Test262 project's testing infrastructure behaves unexpectedly.
2021-05-28 04:13:39 +02:00
"test262-harness": "^8.0.0"
Use travis ci to run new or modified test files on engines
2018-11-06 21:34:53 +01:00
},
"scripts": {
set npm scripts to run tests
2019-04-24 18:17:18 +02:00
"ci": "./tools/scripts/ci_test.sh",
"test": "test262-harness",
Rename usage of master to main Ref #2699
2020-07-15 20:53:19 +02:00
"diff": "git diff --diff-filter ACMR --name-only main.. -- test/ && git ls-files --exclude-standard --others -- test/",
set npm scripts to run tests
2019-04-24 18:17:18 +02:00
"test:diff": "npm run test:diff:v8 && npm run test:diff:spidermonkey && npm run test:diff:chakra && npm run test:diff:javascriptcore",
Fix test:diff npm scripts (#2225) * Include untracked files in `npm run diff` * Suppress non-file output from nested `npm run diff`
2019-07-08 21:32:35 +02:00
"test:diff:v8": "test262-harness -t 8 --hostType=d8 --hostPath=v8 $(npm run --silent diff)",
"test:diff:spidermonkey": "test262-harness -t 8 --hostType=jsshell --hostPath=spidermonkey $(npm run --silent diff)",
"test:diff:chakra": "test262-harness -t 8 --hostType=ch --hostPath=chakra $(npm run --silent diff)",
"test:diff:javascriptcore": "test262-harness -t 8 --hostType=jsc --hostPath=javascriptcore $(npm run --silent diff)",
"test:diff:xs": "test262-harness -t 8 --hostType=xs --hostPath=xs $(npm run --silent diff)"
Use travis ci to run new or modified test files on engines
2018-11-06 21:34:53 +01:00
}
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.
2017-10-02 17:12:14 +02:00
}