v8/test262 at b36cfdb39ae648b49a1396c4f669df9b1f57996c - v8

History

jkummerow b36cfdb39a [test] Fix cctest path separators on Windows Now run-tests.py understands "suite/foo/bar" with forward slashes for command-line test selection on all test suites on all platforms. Previously, file-based suites like mjsunit also accepted "mjsunit/foo\bar"; that behavior is sacrificed here in favor of unification. For the cctest suite, OTOH, it wasn't possible on Windows to select specific tests at all. Review URL: https://codereview.chromium.org/1348653003 Cr-Commit-Position: refs/heads/master@{#30794}		2015-09-17 11:24:09 +00:00
..
harness-adapt.js	Revert of [test] Move test262-es6 into test262. (patchset #2 id:20001 of https://codereview.chromium.org/1215303008/)	2015-07-06 10:35:34 +00:00
README	Revert of [test] Move test262-es6 into test262. (patchset #2 id:20001 of https://codereview.chromium.org/1215303008/)	2015-07-06 10:35:34 +00:00
test262.status	Make Date.prototype an ordinary object	2015-08-31 20:45:48 +00:00
testcfg.py	[test] Fix cctest path separators on Windows	2015-09-17 11:24:09 +00:00

README

This directory contains code for binding the test262 test suite
into the v8 test harness. To use the tests check out the test262
tests from

  https://github.com/tc39/test262

at revision 365 (hash fbba29f) as 'data' in this directory.  Using later
version may be possible but the tests are only known to pass (and indeed run)
with that revision.

  git clone https://github.com/tc39/test262 data
  cd data
  git checkout fbba29f

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.