[Android] Refactor the native test wrappers.

testing/android/native_test/java/src/org/chromium/native_test/NativeBrowserTestActivity.java

Index: testing/android/native_test/java/src/org/chromium/native_test/NativeBrowserTestActivity.java
diff --git a/testing/android/native_test/java/src/org/chromium/native_test/NativeBrowserTestActivity.java b/testing/android/native_test/java/src/org/chromium/native_test/NativeBrowserTestActivity.java
new file mode 100644
index 0000000000000000000000000000000000000000..8083cc009a328ed0d7981d0826f44660f5c34496
--- /dev/null
+++ b/testing/android/native_test/java/src/org/chromium/native_test/NativeBrowserTestActivity.java
@@ -0,0 +1,23 @@
+// Copyright 2015 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.
+
+package org.chromium.native_test;
+
+import android.os.Bundle;
+
+/**
+ * An {@link android.app.Activity} for running native browser tests.
+ */
+public abstract class NativeBrowserTestActivity extends NativeTestActivity {
+
+    @Override
+    public void onCreate(Bundle savedInstanceState) {
+        super.onCreate(savedInstanceState);
+        startBrowser();
+        loadLibraries();

[Ted C, 2015/05/05 23:11:17]

what libraries is it loading here?  this looks backwards to me...shouldn't the
libraries be loaded before the browser is started?

The browser starting also will load a bunch of libraries, so is this duplicated
work?

Looking at the next file it seems like maybe these are the libraries that
contain the test code (maybe)?  Seems like we should figure out a clearer name
here since libraries is pretty overloaded.

[jbudorick, 2015/05/06 18:00:00]

For both browser tests and unit tests, it just appears to be the one .so. (In
the case of, e.g., content_browsertests, that's libcontent_browsertests.so.)
It is. The browser tests do this in LibraryLoader.ensureInitialized.
Moved down to NativeUnitTestActivity.

As it's loading "NativeLibraries.LIBRARIES", I'm not sure how to name it more
specifically...

+    }
+
+    protected abstract void startBrowser();

[Ted C, 2015/05/05 23:11:17]

Add some javadoc here.  Also, does the browser need to be fully running after
returning from this call?

[jbudorick, 2015/05/06 18:00:00]

No. After looking at this more, startBrowser is a misnomer. Renamed to
initializeBrowserProcess, since that more accurately reflects what it does.

+
+}