v8/test/test262
jkummerow 9516dccd41 Reland "[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.

Original review: https://codereview.chromium.org/1348653003/

This reverts commit 5f44a91059.

NOTRY=true

Review URL: https://codereview.chromium.org/1356613002

Cr-Commit-Position: refs/heads/master@{#30798}
2015-09-17 13:01:12 +00:00
..
harness-adapt.js Revert of [test] Move test262-es6 into test262. (patchset 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 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 Reland "[test] Fix cctest path separators on Windows" 2015-09-17 13:01:12 +00:00

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.