Separating the two tests into different executions.

remoting/test/chromoting_test_driver_tests.cc

Index: remoting/test/chromoting_test_driver_tests.cc
diff --git a/remoting/test/chromoting_test_driver_tests.cc b/remoting/test/chromoting_test_driver_tests.cc
index 2216be64ac66dc143984a52585badcc94b3f7d9a..52c58e6686b38bb7759391f2eed1c6cbe1fcceed 100644
--- a/remoting/test/chromoting_test_driver_tests.cc
+++ b/remoting/test/chromoting_test_driver_tests.cc
@@ -15,6 +15,9 @@ const int kMaxTimeToConnectMs = 2000;
 namespace remoting {
 namespace test {
 
+// Note: Make sure to restart the host before running this test. Connecting to
+// a previously connected host will output the time to reconnect versus the time
+// to connect.
 TEST_F(ChromotingTestFixture, TestMeasurePinBasedAuthentication) {
   bool connected = ConnectToHost(kPinBasedMaxConnectionTimeInSeconds);
   EXPECT_TRUE(connected);
@@ -38,6 +41,9 @@ TEST_F(ChromotingTestFixture, TestMeasurePinBasedAuthentication) {
   connection_time_observer_->DisplayConnectionStats();
 }
 
+// Note: Make sure to restart the host before running this test. If the host
+// is not restarted after a previous connection, then the first connection will
+// be a reconnect and the second connection will be a second reconnect.
 TEST_F(ChromotingTestFixture, TestMeasureReconnectPerformance) {
   bool connected = ConnectToHost(kPinBasedMaxConnectionTimeInSeconds);
   EXPECT_TRUE(connected);
@@ -58,8 +64,6 @@ TEST_F(ChromotingTestFixture, TestMeasureReconnectPerformance) {
           protocol::ConnectionToHost::State::CONNECTED).InMilliseconds();
   EXPECT_LE(authenticated_to_connected_time, kMaxTimeToConnectMs);
 
-  connection_time_observer_->DisplayConnectionStats();
-
   // Begin reconnection to same host.
   connected = ConnectToHost(kPinBasedMaxConnectionTimeInSeconds);
   EXPECT_TRUE(connected);