586deecbb1
This patch provides improved infrastructure for developing test262 tests together with V8. It has three parts: - The test262 test runner is updated to look for local versions of tests in the /test/test262/local-tests directory, which mirrors /test/test262/data. Additional tests can be added there and are run together with tests from upstream. Upstream tests can be locally updated by using the same name in local-tests; if a same-named test exists, then only the local version will be run. The local-tests directory is in the V8 repository, unlike the contents of the data directory, so tests can be added in the same patch as something else. - The tool /test/test262/upstream-local-tests.sh is added to create a patch against the test262 respository based on a patch which changes the local-tests directory. - The tool /test/test262/prune-local-tests.sh is added to remove redundant local tests on a test262 roll. See design doc: https://docs.google.com/document/d/16bj7AIDgZLv4WOsUEzQ5NzcEN9_xo095e88Pz8FC5rA/edit Review-Url: https://codereview.chromium.org/2611793002 Cr-Commit-Position: refs/heads/master@{#42117} |
||
|---|---|---|
| .. | ||
| local-tests/test/intl402 | ||
| archive.py | ||
| BUILD.gn | ||
| detachArrayBuffer.js | ||
| harness-adapt.js | ||
| list.py | ||
| prune-local-tests.sh | ||
| README | ||
| test262.gyp | ||
| test262.isolate | ||
| test262.status | ||
| testcfg.py | ||
| upstream-local-tests.sh | ||
This directory contains code for binding the test262 test suite into the v8 test harness. The tests are checked out as a dependency from https://chromium.googlesource.com/external/github.com/tc39/test262 at a revision specified in the DEPS file as 'data' in this directory. They are fetched with 'gclient sync'. To update to a newer version, please change the DEPS file. Using a newer version, e.g. 'deadbeef' may be possible but the tests are only known to pass (and indeed run) with the DEPS revision. Example: cd data git fetch git checkout deadbeef If you do update to a newer revision you may have to change the test harness adapter code since it uses internal functionality from the harness that comes bundled with the tests. You will most likely also have to update the test expectation file.