marja@chromium.org 14a90fcc57 Better tests for the Parser / Preparser unification. ... We need a way to assert that for a given source code snippet, an error *is* produced or *is not* produced. Otherwise we might accidentally create new errors or start accepting code which was previously not accepted. Just checking that Parser and PreParser produce the same result doesn't cut it. BUG=3126 LOG=N R=ulan@chromium.org Review URL: https://codereview.chromium.org/154243005 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@19107 ce2b1a6d-e550-0410-aec6-3dcde31c8c00		2014-02-05 15:30:01 +00:00
..
benchmarks	Update benchmark test suite.	2013-11-20 15:05:52 +00:00
cctest	Better tests for the Parser / Preparser unification.	2014-02-05 15:30:01 +00:00
intl	Implements ES6 String.prototype.normalize method.	2014-01-31 08:09:17 +00:00
message	Make sure files end with exactly one new line and police this in presubmit.	2013-11-22 13:50:39 +00:00
mjsunit	Move failing ASSERT on ARM to a more sane place.	2014-02-05 10:12:14 +00:00
mozilla	Skip Mozilla tests with timeouts.	2014-01-29 15:13:45 +00:00
preparser	Make sure files end with exactly one new line and police this in presubmit.	2013-11-22 13:50:39 +00:00
test262	Remove CallICs	2014-01-31 16:52:17 +00:00
webkit	Tests for (pre)parse errors when "eval" and "arguments" are found in inappropriate places.	2014-02-04 11:26:19 +00:00