More integration tests for analysis server.

More integration tests for analysis server.

This covers everything in the "server" domain except for server.error
(which is difficult to test since it should only occur in the event of
a server bug).

R=brianwilkerson@google.com

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

[Brian Wilkerson, 2014-07-16 21:47:32]

LGTM

https://codereview.chromium.org/396383002/diff/1/pkg/analysis_server/test/int...
File pkg/analysis_server/test/integration/server_domain_inttest.dart (right):

https://codereview.chromium.org/396383002/diff/1/pkg/analysis_server/test/int...
pkg/analysis_server/test/integration/server_domain_inttest.dart:86: // that this
notification should only occur in the event of a server bug?
What is it about this notification that you want to test?

[Paul Berry, 2014-07-16 23:43:25]

https://codereview.chromium.org/396383002/diff/1/pkg/analysis_server/test/int...
File pkg/analysis_server/test/integration/server_domain_inttest.dart (right):

https://codereview.chromium.org/396383002/diff/1/pkg/analysis_server/test/int...
pkg/analysis_server/test/integration/server_domain_inttest.dart:86: // that this
notification should only occur in the event of a server bug?
On 2014/07/16 21:47:32, Brian Wilkerson wrote:
> What is it about this notification that you want to test?

It would be nice if we could find a way to test that when an exception occurs in
the server, the message that gets sent upstream satisfies the API definition
(i.e. it contains a 'fatal' field which is a bool, a 'message' field which is a
string, a 'stackTrace' field which is a string, and no other fields).  That
would at least help reassure us that if an exception should ever occur in
production use, the client will be able to parse it.

[Paul Berry, 2014-07-16 23:46:43]

Committed patchset #1 manually as r38319 (presubmit successful).