Add initial Chromium TestShell support for Android

chrome/android/testshell/chrome_main_delegate_testshell_android.cc

+// Copyright (c) 2012 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 "chrome/android/testshell/chrome_main_delegate_testshell_android.h"
+
+#include "base/android/jni_android.h"
+
+ChromeMainDelegateTestShellAndroid::ChromeMainDelegateTestShellAndroid() {
+}
+
+ChromeMainDelegateTestShellAndroid::~ChromeMainDelegateTestShellAndroid() {
+}
+
+bool ChromeMainDelegateTestShellAndroid::RegisterApplicationNativeMethods(
+    JNIEnv* env) {
+  // Register the generic Chrome JNI methods first.  If that succeeds,
+  // proceed to register any extra JNI methods here.
+  if (!ChromeMainDelegateAndroid::RegisterApplicationNativeMethods(env))
+    return false;
+
+  // Add extra JNI methods if necessary here.

[Yaron, 2012/09/07 20:53:43]

Are there really going to be others? I think you can just do:
return ChromeMainDelegateAndroid::RegisterApplicationNativeMethods(env);

[David Trainor- moved to gerrit, 2012/09/10 18:09:13]

For the rendering and tab components I already have two more in a CL downstream.
 The tab component will eventually be rolled into the common lib but the
rendering might not.  I can remove this comment and just add them when I get to
them though.

On 2012/09/07 20:53:43, Yaron wrote:

+
+  return true;
+}