Updated latency fixture and refactored connection helper

remoting/test/app_remoting_connection_helper.h

Index: remoting/test/app_remoting_connection_helper.h
diff --git a/remoting/test/app_remoting_connection_helper.h b/remoting/test/app_remoting_connection_helper.h
index 6978747688b9d603c9452be8304f6523ab14d818..6c14a28cb3e7ad90f4617d3b9b80aca3affaada8 100644
--- a/remoting/test/app_remoting_connection_helper.h
+++ b/remoting/test/app_remoting_connection_helper.h
@@ -25,10 +25,6 @@ namespace test {
 struct RemoteApplicationDetails;
 class TestChromotingClient;
 
-// Allows for custom handling of ExtensionMessage messages.
-typedef base::Callback<void(const protocol::ExtensionMessage& message)>
-    HostMessageReceivedCallback;
-
 // Creates a connection to a remote host which is available for tests to use.
 // A TestChromotingClient is required from caller.
 class AppRemotingConnectionHelper
@@ -51,10 +47,11 @@ class AppRemotingConnectionHelper
   protocol::HostStub* host_stub();
   protocol::InputStub* input_stub();
 
-  // Setter for |host_message_received_callback_|.
-  void SetHostMessageReceivedCallback(
-      HostMessageReceivedCallback host_message_received_callback);
+  // Returns the test chromoting client.
+  // NOTE: Caller should not release the object.
+  TestChromotingClient* GetTestChromotingClient() { return client_.get(); }

[joedow, 2015/07/27 17:30:12]

This should use the unix_hacker_style() naming convention:
https://www.chromium.org/developers/coding-style

Simple accessors should generally be the only inline functions. These should be
named unix_hacker_style().

This is consistent with the host_stub and input_stub methods above.

[liaoyuke, 2015/07/27 17:40:45]

Done.

 
+  // Returns true if connection is ready for tests.
   bool ConnectionIsReadyForTest() { return connection_is_ready_for_tests_; }
 
  private:
@@ -74,10 +71,6 @@ class AppRemotingConnectionHelper
   // Contains the details for the application being tested.
   const RemoteApplicationDetails& application_details_;
 
-  // Called when an ExtensionMessage is received from the host.  Used to
-  // override default message handling.
-  HostMessageReceivedCallback host_message_received_callback_;
-
   // Indicates whether the remote connection is ready to be used for testing.
   // True when a chromoting connection to the remote host has been established
   // and the main application window is visible.