v8/test262 at 089e4fd32c838f2ec6a001d8db7b8b227936b250 - v8

History

henrique.ferreiro afd5ff553b Install the 'name' property in classes at runtime This allows to detect a static property also named 'name', and also makes sure 'name' is added last, to be standards-compliant. BUG=v8:4199 Review-Url: https://codereview.chromium.org/2423053002 Cr-Commit-Position: refs/heads/master@{#41546}		2016-12-07 10:35:00 +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 roll	2016-10-20 10:29:28 +00:00
README	Make test262 README file revision independent.	2015-11-04 10:52:44 +00:00
test262.gyp	test262 roll	2016-10-20 10:29:28 +00:00
test262.isolate	test262 roll	2016-05-02 23:02:38 +00:00
test262.status	Install the 'name' property in classes at runtime	2016-12-07 10:35:00 +00:00
testcfg.py	[modules] Update test262 config and status file.	2016-10-10 17:38:56 +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.