Fix thread usage in chromoting host

remoting/host/chromoting_host_context_unittest.cc

Index: remoting/host/chromoting_host_context_unittest.cc
diff --git a/remoting/host/chromoting_host_context_unittest.cc b/remoting/host/chromoting_host_context_unittest.cc
new file mode 100644
index 0000000000000000000000000000000000000000..6b481d7a18cbc79f5c015a7f7f4a63cc8cc20dfc
--- /dev/null
+++ b/remoting/host/chromoting_host_context_unittest.cc
@@ -0,0 +1,28 @@
+// Copyright (c) 2010 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "base/message_loop.h"
+#include "remoting/host/chromoting_host_context.h"
+#include "testing/gtest/include/gtest/gtest.h"
+
+namespace remoting {
+
+// A simple test that starts and stop the context. This tests the context
+// operates properly and all threads and message loops are valid.
+TEST(ChromotingHostContextTest, StartAndStop) {
+  ChromotingHostContext context;
+  context.Start();
+  EXPECT_TRUE(context.jingle_thread());
+  EXPECT_TRUE(context.main_message_loop());
+  EXPECT_TRUE(context.capture_message_loop());
+  EXPECT_TRUE(context.encode_message_loop());
+  context.Stop();
+
+  // Expect all the threads are stopped.
+  EXPECT_FALSE(context.main_thread_.IsRunning());
+  EXPECT_FALSE(context.capture_thread_.IsRunning());
+  EXPECT_FALSE(context.encode_thread_.IsRunning());
+}
+
+}  // namespace remoting