Adding container class for chromoting client runtimes.

remoting/client/chromoting_client_runtime_unittest.cc

+// Copyright (c) 2016 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/message_loop.h"
+#include "base/run_loop.h"
+#include "remoting/base/auto_thread_task_runner.h"
+#include "remoting/client/chromoting_client_runtime.h"
+#include "testing/gtest/include/gtest/gtest.h"
+
+namespace remoting {
+
+// A simple test that starts and stop the runtime. This tests the runtime
+// operates properly and all threads and message loops are valid.
+TEST(ChromotingClientRuntimeTest, StartAndStop) {
+  base::MessageLoopForUI message_loop;
+  base::RunLoop run_loop;
+
+  scoped_ptr<ChromotingClientRuntime> runtime =
+    ChromotingClientRuntime::Create();
+
+  EXPECT_TRUE(runtime);

[Lambros, 2016/03/09 00:06:18]

EXPECT_TRUE(x); if (!x) return;
can be replaced with
ASSERT_TRUE(x);

[nicholss, 2016/03/09 16:54:27]

Done.

+  if (!runtime)
+    return;
+  EXPECT_TRUE(runtime->network_task_runner().get());
+  EXPECT_TRUE(runtime->ui_task_runner().get());
+  EXPECT_TRUE(runtime->display_task_runner().get());
+  EXPECT_TRUE(runtime->file_task_runner().get());
+  EXPECT_TRUE(runtime->url_requester().get());
+
+  runtime.reset();

[Lambros, 2016/03/09 00:06:18]

This line is a no-op, |runtime| goes out of scope here anyway?

[nicholss, 2016/03/09 16:54:28]

Done.

+}
+
+}  // namespace remoting