Better tests for the Parser / Preparser unification.

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

Committed: https://code.google.com/p/v8/source/detail?r=19107

[ulan, 2014-02-05 15:00:10]

lgtm

https://codereview.chromium.org/154243005/diff/1/test/cctest/test-parsing.cc
File test/cctest/test-parsing.cc (right):

https://codereview.chromium.org/154243005/diff/1/test/cctest/test-parsing.cc#...
test/cctest/test-parsing.cc:1116: bool assert_success,
Maybe enum is better than two flags? Looks like they are encoding three possible
cases.

[marja, 2014-02-05 15:28:12]

https://codereview.chromium.org/154243005/diff/1/test/cctest/test-parsing.cc
File test/cctest/test-parsing.cc (right):

https://codereview.chromium.org/154243005/diff/1/test/cctest/test-parsing.cc#...
test/cctest/test-parsing.cc:1116: bool assert_success,
On 2014/02/05 15:00:10, ulan wrote:
> Maybe enum is better than two flags? Looks like they are encoding three
possible
> cases.

Done.

[marja, 2014-02-05 15:30:09]

Committed patchset #2 manually as r19107 (presubmit successful).

[ulan, 2014-02-05 15:30:34]

lgtm