Update test utils to generate wrappers with new library syntax and handle

Update test utils to generate wrappers with new library syntax and handle
tests with new library syntax.
Committed: https://code.google.com/p/dart/source/detail?r=14437

[gram, 2012-11-01 20:55:40]

Separated out as per Peter's suggestion.

[Siggi Cherem (dart-lang), 2012-11-01 21:02:04]

not sure if matching things exactly is necessary given that we'll soon deprecate
#source, but I'm OK with it if Bill agrees.

https://codereview.chromium.org/11358045/diff/1/tools/testing/dart/test_suite...
File tools/testing/dart/test_suite.dart (right):

https://codereview.chromium.org/11358045/diff/1/tools/testing/dart/test_suite...
tools/testing/dart/test_suite.dart:984: const
RegExp(r"^[#]?(source|part|import|resource)", multiLine: true);
I think resource is gone. Also this matches more than we want (e.g. it matches
"source 'foo.dart'" and "#part('foo.dart')".

https://codereview.chromium.org/11358045/diff/1/tools/testing/dart/test_suite...
tools/testing/dart/test_suite.dart:1045: !partofRegExp.hasMatch(contents);
alternative you could include a ['"] in the match of import/part?

[ahe, 2012-11-01 21:08:42]

lgtm

https://codereview.chromium.org/11358045/diff/1/tools/testing/dart/test_suite...
File tools/testing/dart/test_suite.dart (right):

https://codereview.chromium.org/11358045/diff/1/tools/testing/dart/test_suite...
tools/testing/dart/test_suite.dart:984: const
RegExp(r"^[#]?(source|part|import|resource)", multiLine: true);
On 2012/11/01 21:02:04, Siggi Cherem (dart-lang) wrote:
> I think resource is gone. Also this matches more than we want (e.g. it matches
> "source 'foo.dart'" and "#part('foo.dart')". 

I don't think it matters. There are good chances we can get rid of wrapping this
month.

[gram, 2012-11-01 21:20:48]

PTAL

https://codereview.chromium.org/11358045/diff/1/tools/testing/dart/test_suite...
File tools/testing/dart/test_suite.dart (right):

https://codereview.chromium.org/11358045/diff/1/tools/testing/dart/test_suite...
tools/testing/dart/test_suite.dart:984: const
RegExp(r"^[#]?(source|part|import|resource)", multiLine: true);
Yes, these false positives are very unlikely to happen in our tests, and once
the # directives are not supported these regexps can be cleaned up; it doesn't
seem worth getting too fussy about them. But I have cleaned them up a bit so
that it isn't necessary to have the partof Regexp.

[Siggi Cherem (dart-lang), 2012-11-01 21:22:57]

lgtm

[ahe, 2012-11-01 21:23:44]

lgtm

https://codereview.chromium.org/11358045/diff/6001/tools/testing/dart/browser...
File tools/testing/dart/browser_test.dart (right):

https://codereview.chromium.org/11358045/diff/6001/tools/testing/dart/browser...
tools/testing/dart/browser_test.dart:58: import
'${dartHome.append('pkg/unittest/lib/unittest.dart')}' as unittest;
Perhaps you should remove the '/lib' part until the other CL lands.