Enable co19 test suite on dart test scripts.

Enable co19 test suite on dart test scripts.

Updated the TestExpectations class to be able to deal with the
odd matching rules that are used for co19.

Currently we are using a lot of memory when running all of these
tests. I have optimized the test expectation part quite a bit.
The thing that seems bad now if the processing of all the lines
of every simple test to find DartOptions. We need to work on that.

R=whesse@google.com
BUG=
TEST=

Committed: https://code.google.com/p/dart/source/detail?r=1563

[Bill Hesse, 2011-11-16 11:44:27]

We already have support for negative tests, in the test runner and TestCase and
TestOutput classes.  I think we should use it, so that the progress monitors
don't report negative tests as "Fail".

Otherwise, LGTM.

http://codereview.chromium.org/8539044/diff/1/tests/co19/test_config.dart
File tests/co19/test_config.dart (right):

http://codereview.chromium.org/8539044/diff/1/tests/co19/test_config.dart#new...
tests/co19/test_config.dart:92: completeHandler,
Insert "isNegative" argument to constructor, and pass
optionsFromFile["isNegative"] here.

http://codereview.chromium.org/8539044/diff/1/tests/co19/test_config.dart#new...
tests/co19/test_config.dart:107: 
We have handling for this in the test runner already.  You should set a negative
flag in the TestCase, so that TestCase.isNegative (a getter) returns true.  This
way, the counts of "Fail" are not artificially increased.

[Mads Ager (google), 2011-11-16 12:26:38]

http://codereview.chromium.org/8539044/diff/1/tests/co19/test_config.dart
File tests/co19/test_config.dart (right):

http://codereview.chromium.org/8539044/diff/1/tests/co19/test_config.dart#new...
tests/co19/test_config.dart:107: 
On 2011/11/16 11:44:27, Bill Hesse wrote:
> We have handling for this in the test runner already.  You should set a
negative
> flag in the TestCase, so that TestCase.isNegative (a getter) returns true. 
This
> way, the counts of "Fail" are not artificially increased.

Good point. Done.