Speed up web_socket_test by running subtests in parallel.

Speed up web_socket_test by running subtests in parallel.


BUG=

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

[Anders Johnsen, 2013-01-17 12:41:57]

As discussed offline, I don't think we should pipeline tests at all. Up to you
though, so let me know! :)

[Bill Hesse, 2013-01-17 12:59:38]

Removed pipelining.

[Anders Johnsen, 2013-01-17 14:17:33]

LGTM

https://codereview.chromium.org/11946042/diff/4001/tests/standalone/io/web_so...
File tests/standalone/io/web_socket_test.dart (right):

https://codereview.chromium.org/11946042/diff/4001/tests/standalone/io/web_so...
tests/standalone/io/web_socket_test.dart:20: ReceivePort keepAlive = new
ReceivePort();
The ReceivePorts are redundant in some of these tests. I would suggest that we
try to avoid redundant code in tests. Your choice.

https://codereview.chromium.org/11946042/diff/4001/tests/standalone/io/web_so...
tests/standalone/io/web_socket_test.dart:21: HttpServer server = secure ? new
HttpsServer() : new HttpServer();
Move all of this out to a

createServer();

ditto for createClient, HttpClientConnection/HttpClient.

https://codereview.chromium.org/11946042/diff/4001/tests/standalone/io/web_so...
tests/standalone/io/web_socket_test.dart:422: InitializeSSL();
initializeSSL

https://codereview.chromium.org/11946042/diff/4001/tests/standalone/io/web_so...
tests/standalone/io/web_socket_test.dart:424: runTests();
Put in secure == null below, so we can check that connections are created when
we expect them.