apk-based test runner work. Not enabled yet. This CL is a combination of upstreaming, ndk/ant-ifi…

base/test/android/AndroidManifest.xml

Index: base/test/android/AndroidManifest.xml
diff --git a/base/test/android/AndroidManifest.xml b/base/test/android/AndroidManifest.xml
new file mode 100644
index 0000000000000000000000000000000000000000..5e154a0ca56def026f637e55875c30f55d151c5f
--- /dev/null
+++ b/base/test/android/AndroidManifest.xml
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="utf-8"?>

[klobag.chromium, 2012/03/28 00:28:57]

Need copyright.

+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+      package="org.chromium.native_test"

[klobag.chromium, 2012/03/28 00:28:57]

should this be org.chromium.base.native_test? In Android, package name is
unique. So we can't run base unittest together with net unittest.

+      android:versionCode="1"
+      android:versionName="1.0">
+
+    <!-- This is the platform API where NativeActivity was introduced. -->

[Satish, 2012/03/27 13:53:24]

In ChromeNativeTestActivity.java we don't seem to be using NativeActivity and
have a comment indicating it won't be used in future. Should this comment be
removed?

+    <uses-sdk android:minSdkVersion="14" />
+
+    <application android:label="ChromeNativeTest">
+        <activity android:name=".ChromeNativeTestActivity"
+                android:label="ChromeNativeTest"
+                android:configChanges="orientation|keyboardHidden">
+            <intent-filter>
+                <action android:name="android.intent.action.MAIN" />
+                <category android:name="android.intent.category.LAUNCHER" />
+            </intent-filter>
+        </activity>
+    </application>
+
+    <uses-permission android:name="android.permission.INTERNET"/>
+    <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
+    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
+    <uses-permission android:name="android.permission.ACCESS_MOCK_LOCATION" />
+    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
+    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
+    <uses-permission android:name="android.permission.VIBRATE"/>

[klobag.chromium, 2012/03/28 00:28:57]

Why we need VIBRATE for the base unit test?

Should we review all this permissions?

+    <uses-permission android:name="android.permission.GET_ACCOUNTS"/>
+    <uses-permission android:name="android.permission.USE_CREDENTIALS"/>
+    <uses-permission android:name="android.permission.READ_CONTACTS"/>
+    <uses-permission android:name="android.permission.READ_PHONE_STATE"/>
+    <uses-permission android:name="android.permission.READ_LOGS"/>
+    <uses-permission android:name="com.android.browser.permission.READ_HISTORY_BOOKMARKS"/>
+    <uses-permission android:name="com.android.browser.permission.WRITE_HISTORY_BOOKMARKS"/>
+    <uses-permission android:name="android.permission.SUBSCRIBED_FEEDS_READ"/>
+    <uses-permission android:name="android.permission.SUBSCRIBED_FEEDS_WRITE" />
+    <uses-permission android:name="android.permission.READ_SYNC_STATS"/>
+    <uses-permission android:name="android.permission.READ_SYNC_SETTINGS"/>
+    <uses-permission android:name="android.permission.WRITE_SYNC_SETTINGS"/>
+    <uses-permission android:name="android.permission.RECORD_AUDIO"/>
+    <uses-permission android:name="android.permission.WAKE_LOCK"/>
+
+</manifest>