Add apps_browsertests target (currently running 0 tests).

apps/test/apps_test_launcher_delegate.cc

+// Copyright 2014 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 "apps/test/apps_test_launcher_delegate.h"
+
+#include "apps/shell/app/shell_main_delegate.h"
+#include "apps/test/apps_test_suite_base.h"
+#include "base/command_line.h"
+#include "content/public/app/content_main_delegate.h"

[jam, 2014/03/20 16:58:13]

nit: not needd. also the previous include i think as well

[Yoyo Zhou, 2014/03/20 21:17:30]

Done.

+
+namespace apps {
+
+int AppsTestLauncherDelegate::RunTestSuite(int argc, char** argv) {
+  return AppsTestSuiteBase(argc, argv).Run();

[jam, 2014/03/20 16:58:13]

just call content::ContentTestSuiteBase(argc, argv).Run() directly and remove
apps_test_suite_base.* 

In content, we have apps_test_suite_base because we share it with unit tests and
content browser tests. or at least, before my recent refactoring which you saw,
we needed to share some code. but now we don't, and i'm planning on removing
that base class.

if you create apps_unittests, then you can create a test suite for unittests,
but you shouldn't need one for browser tests. that's not needed because now the
browser test harness sets up everything by calling contentmain.

[Yoyo Zhou, 2014/03/20 21:17:30]

Why is ContentTestSuiteBase's constructor protected?

I'm going to try base::TestSuite instead.

[jam, 2014/03/20 23:43:22]

I think because before, you always needed to derive from it.
sg, i just looked and there's nothing from there (ContentTestSuiteBase) that you
should need

+}
+
+bool AppsTestLauncherDelegate::AdjustChildProcessCommandLine(
+    base::CommandLine* command_line,
+    const base::FilePath& temp_data_dir) {
+  return true;
+}
+
+content::ContentMainDelegate*
+AppsTestLauncherDelegate::CreateContentMainDelegate() {
+  return new ShellMainDelegate();
+}
+
+}  // namespace apps