mojo: Delay ApplicationTestBase shell disconnection.

mojo/shell/public/cpp/lib/application_test_base.cc

Index: mojo/shell/public/cpp/lib/application_test_base.cc
diff --git a/mojo/shell/public/cpp/lib/application_test_base.cc b/mojo/shell/public/cpp/lib/application_test_base.cc
index f9a726dbf2c752e033d1e331ba1d9d8d0ac06338..e282822c042198baae8959b11a51791626b9e27c 100644
--- a/mojo/shell/public/cpp/lib/application_test_base.cc
+++ b/mojo/shell/public/cpp/lib/application_test_base.cc
@@ -161,8 +161,6 @@ void ApplicationTestBase::TearDown() {
   CHECK(!g_shell_client_request.is_pending());
   CHECK(!g_shell);
 
-  test_helper_.reset();
-
   if (ShouldCreateDefaultRunLoop())
     Environment::DestroyDefaultRunLoop();

[msw, 2016/02/23 18:02:42]

Does the order of closing the connection and destroying the run loop matter?

[msw, 2016/02/23 18:03:44]

Sorry, ignore this old comment.

[xhwang, 2016/02/23 18:05:39]

Actually it's a good question, and I don't know enough to answer that. It
doesn't matter here since I am not changing the order, but it'd be interesting
to know :)

 }