v8/test262 at eca42c42cb6508b7979f70722a4c3632bf54843e - v8

History

machenbach@chromium.org eca42c42cb Revert "Turn on i18n support by default", "Update test262 expectations, now that 15.5.4.9_CE passes", "Make testing i18n the default.", "Mark two failing mozilla tests as failing.", "Mark mozilla tests as flaky instead of failing" and "Fix test expectations for i18n." This reverts commit 16783-16788 due to several crashers on nosnap builder. TBR=jochen@chromium.org Review URL: https://codereview.chromium.org/23455055 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16789 ce2b1a6d-e550-0410-aec6-3dcde31c8c00		2013-09-18 13:50:00 +00:00
..
harness-adapt.js	Updated status file for test262 to latest revision.	2011-07-09 07:29:32 +00:00
README	Update Test262 harness to recent version.	2013-05-10 13:00:43 +00:00
test262.status	Revert "Turn on i18n support by default", "Update test262 expectations, now that 15.5.4.9_CE passes", "Make testing i18n the default.", "Mark two failing mozilla tests as failing.", "Mark mozilla tests as flaky instead of failing" and "Fix test expectations for i18n."	2013-09-18 13:50:00 +00:00
testcfg.py	Update Test262 harness to recent version.	2013-05-10 13:00:43 +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

  http://hg.ecmascript.org/tests/test262

at revision 365 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.

hg clone -r 365 http://hg.ecmascript.org/tests/test262 data

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.