v8/test262 at e99d292909f4a2ad055bfce16ce96018d816fa8f - v8

History

littledan e99d292909 Base the right RegExp brand checks on Symbol.match The ES2015 specification requires that String.prototype.startsWith, String.prototype.endsWith and String.prototype.includes use the IsRegExp internal algorithm to determine whether to throw a TypeError to prevent a RegExp from being accidentally cast to a String for those methods. That internal algorithm checks the presence/truthiness of Symbol.match to make its determination. This patch switches the builtins to use this correct test, rather than checking for the [[RegExpMatcher]] internal slot as the builtins previously did. R=yangguo Review URL: https://codereview.chromium.org/1762183002 Cr-Commit-Position: refs/heads/master@{#34547}		2016-03-07 16:05:56 +00:00
..
archive.py	[Swarming] work around slow calls in archive.py	2016-02-24 11:04:22 +00:00
harness-adapt.js	[test] Copy test262-es6 into test262.	2015-09-25 13:03:36 +00:00
list.py	[Swarming] Speed up test262 upload/download.	2016-02-19 14:41:29 +00:00
README	Make test262 README file revision independent.	2015-11-04 10:52:44 +00:00
test262.gyp	[Swarming] Speed up test262 upload/download.	2016-02-19 14:41:29 +00:00
test262.isolate	[Swarming] Speed up test262 upload/download.	2016-02-19 14:41:29 +00:00
test262.status	Base the right RegExp brand checks on Symbol.match	2016-03-07 16:05:56 +00:00
testcfg.py	[Swarming] Correctly handle test262 archiving for local checkouts.	2016-02-28 12:27:26 +00:00

README

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.