v8/test/test262
Michal Majewski b43550b7ee [test] Share output procs in mozilla and test262
Bug: v8:6917
Cq-Include-Trybots: master.tryserver.v8:v8_linux_noi18n_rel_ng
Change-Id: I8783192268cc0860b553af418d56f1117817d747
Reviewed-on: https://chromium-review.googlesource.com/836609
Commit-Queue: Michał Majewski <majeski@google.com>
Reviewed-by: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#50241}
2017-12-20 16:08:19 +00:00
..
local-tests/test [intl] fix off-by-1 in NumberFormat formatToParts parameter parsing 2017-09-18 20:07:23 +00:00
archive.py Reland of [test] Speculatively remove local-tests from archive (patchset #1 id:1 of https://codereview.chromium.org/2640223003/ ) 2017-02-28 14:43:15 +00:00
BUILD.gn
detachArrayBuffer.js test262 roll 2017-03-13 14:33:07 +00:00
harness-adapt.js test262 roll 2017-03-13 14:33:07 +00:00
harness-agent.js Make test262 agent more strict in broadcast/report 2017-07-07 21:38:31 +00:00
list.py test262 roll 2017-03-13 14:33:07 +00:00
prune-local-tests.sh test262 roll 2017-02-10 19:05:55 +00:00
README
test262.gyp
test262.isolate Reland of [test] Speculatively remove local-tests from archive (patchset #1 id:1 of https://codereview.chromium.org/2640223003/ ) 2017-02-28 14:43:15 +00:00
test262.status test262 roll 2017-12-11 20:41:40 +00:00
testcfg.py [test] Share output procs in mozilla and test262 2017-12-20 16:08:19 +00:00
upstream-local-tests.sh test262 roll 2017-03-13 14:33:07 +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.