Add automated VR latency tester

BUILD.gn

Index: BUILD.gn
diff --git a/BUILD.gn b/BUILD.gn
index 7bce8b892e062ae127feba2d0c19b245178064b9..4b1ba66add3f5d45e470e0aafb8d51823dcbd381 100644
--- a/BUILD.gn
+++ b/BUILD.gn
@@ -696,7 +696,10 @@ group("gn_all") {
   }
 
   if (is_android) {
-    deps += [ "//build/android/gyp/test:hello_world" ]
+    deps += [
+      "//build/android/gyp/test:hello_world",
+      "//chrome/test/vr/automated_motopho_latency:automated_motopho_latency_test",

[Lei Lei, 2017/04/07 21:36:34]

Why do you add automated_motopho_latency_test target to gn_all target?

I think we can compile automated_motopho_latency_test directly.

[bsheedy, 2017/04/07 23:24:51]

From the top of the file:
"So if you add a new build file, there must be some path of dependencies from
this file to the new one or GN won't know about it."

There might be a better way of meeting this requirement, but there needs to be
some path from //BUILD.gn to
//chrome/test/vr/automated_motopho_latency/BUILD.gn. I considered just making
the test a part of //chrome/android's BUILD.gn, but since this should be
applicable to desktop as well in the future, this seemed like a better approach.

+    ]
   }
 
   if (is_linux && use_ozone) {