Setup JS unittests for Chromoting

chrome/test/run_all_unittests.cc

Index: chrome/test/run_all_unittests.cc
diff --git a/chrome/test/run_all_unittests.cc b/chrome/test/run_all_unittests.cc
new file mode 100644
index 0000000000000000000000000000000000000000..8567cf9ba5815f2d162d78f995d9264883153517
--- /dev/null
+++ b/chrome/test/run_all_unittests.cc
@@ -0,0 +1,21 @@
+// Copyright (c) 2011 The Chromium Authors. All rights reserved.

[Sheridan Rawlins, 2011/11/21 22:13:15]

There's already a chrome/test/base/run_all_unittests.cc  How is this different,
and is it different enough to merit its own executable?  Why just build
chromoting tests into unit_tests?  Minimally, can the same
chrome/test/base/run_all_unittests.cc be used for both?

+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+// A basic testrunner that supports JavaScript unittests.
+// This lives in src/chrome/test so that:
+//  (1) it can be shared by different subprojects,
+//  (2) it can include chrome_paths.h (required for JS unittests) without
+//      updating the DEPS file for each subproject.
+
+#include "base/test/test_suite.h"
+#include "chrome/common/chrome_paths.h"
+
+int main(int argc, char** argv) {
+  base::TestSuite test_suite(argc, argv);
+
+  // This is required for the JavaScript unittests.
+  chrome::RegisterPathProvider();
+
+  return test_suite.Run();
+}