041c009d9b
DesignDoc: https://goo.gl/ZAtL1f Chrome Status: https://www.chromestatus.com/feature/5430420699086848 I2I: http://shorturl.at/sE168 I2S: http://shorturl.at/qsHU9 Bug: v8:8518 Change-Id: Ib9d6ce4782c12745d3d44500991074646254621a Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1639698 Commit-Queue: Frank Tang <ftang@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/master@{#62039} |
||
---|---|---|
.. | ||
local-tests/test | ||
BUILD.gn | ||
detachArrayBuffer.js | ||
harness-adapt-donotevaluate.js | ||
harness-adapt.js | ||
harness-agent.js | ||
OWNERS | ||
prune-local-tests.sh | ||
README | ||
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.