v8/test/test262
mstarzinger c22e4278ec [interpreter] Module tests in all Ignition variants.
This makes sure we run the module tests against all variants using
Ignition as the first compilation tier. It will henceforth extend the
test coverage to the BytecodeGraphBuilder as well.

R=neis@chromium.org

Review-Url: https://codereview.chromium.org/2397733002
Cr-Commit-Position: refs/heads/master@{#39992}
2016-10-05 13:06:09 +00:00
..
archive.py [test262] Use standalone Test262 harness project 2016-07-22 15:25:32 +00:00
BUILD.gn [gn] Port test262 archiving to gn 2016-06-06 08:56:58 +00:00
detachArrayBuffer.js This patch updates to the latest test262 version 2016-09-01 17:43:31 +00:00
harness-adapt.js This patch updates to the latest test262 version 2016-09-01 17:43:31 +00:00
list.py [test262] Use standalone Test262 harness project 2016-07-22 15:25:32 +00:00
README
test262.gyp [gn] Move build to gypfiles 2016-04-29 10:11:11 +00:00
test262.isolate test262 roll 2016-05-02 23:02:38 +00:00
test262.status [interpreter] Module tests in all Ignition variants. 2016-10-05 13:06:09 +00:00
testcfg.py [test] Deprecate test data download for most test suites 2016-08-08 12:39:48 +00:00

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.