[Android] Create a dummy app to upload to Appurify for gtests.

build/android/pylib/remote/device/dummy/dummy.gyp

Index: build/android/pylib/remote/device/dummy/dummy.gyp
diff --git a/build/android/pylib/remote/device/dummy/dummy.gyp b/build/android/pylib/remote/device/dummy/dummy.gyp
new file mode 100644
index 0000000000000000000000000000000000000000..4d94a394fbdd33da854fc9188ae731bfc90f5efa
--- /dev/null
+++ b/build/android/pylib/remote/device/dummy/dummy.gyp
@@ -0,0 +1,24 @@
+# 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.
+
+# Running Robotium tests on AMP requires both an "app" APK and a "test" APK

[klundberg, 2015/01/06 18:17:31]

"Robotium" can be a little confusing as we won't actually run Robotium tests at
all. I know that is what AMP uses but maybe you could make this comment a little
less "implementation specific" to avoid confusion?

[jbudorick, 2015/01/06 18:25:57]

The issue with that is that the entire reason for this target _is_
implementation specific - AMP's "robotium" test type _requires_ an app APK and a
test APK.

+# with different package names. Our gtests only use one APK, so we build a
+# dummy APK to upload as the app.
+
+{
+  'targets': [
+    {
+      'target_name': 'remote_device_dummy_apk',
+      'type': 'none',
+      'variables': {
+        'apk_name': 'remote_device_dummy',
+        'java_in_dir': '.',
+        'android_manifest_path': '../../../../../../build/android/AndroidManifest.xml',
+      },
+      'includes': [
+        '../../../../../../build/java_apk.gypi',
+      ]
+    },
+  ]
+}