Make VR latency results compatible with perf dashboard, refactor into classes

chrome/test/vr/perf/latency/BUILD.gn

Index: chrome/test/vr/perf/latency/BUILD.gn
diff --git a/chrome/test/vr/perf/latency/BUILD.gn b/chrome/test/vr/perf/latency/BUILD.gn
index 6e158dd02f35b72221629f467818a52dd7f614b6..bedbcb71c89a4e275a9a7fd77d2689e815af6c09 100644
--- a/chrome/test/vr/perf/latency/BUILD.gn
+++ b/chrome/test/vr/perf/latency/BUILD.gn
@@ -5,7 +5,13 @@
 group("motopho_latency_test") {
   testonly = true
   data = [
+    "./__init__.py",
+    "./android_webvr_latency_test.py",
+    "./motopho_thread.py",
+    "./robot_arm.py",
     "./run_latency_test.py",
+    "./webvr_latency_test.py",

[Lei Lei, 2017/04/17 22:57:13]

You can add all the files in one folder as data, but I am not sure how to add
current folder, maybe
data = [
  "./",
]

See https://cs.chromium.org/chromium/src/chrome/test/media_router/BUILD.gn?l=10

[bsheedy, 2017/04/18 21:17:25]

./ works, and I had that before, but changed it to individual files so that the
BUILD.gn file wouldn't be included. Including it doesn't cause any issues, but
might as well skip it if it's easy to do so.

We could move the BUILD.gn file to chrome/test/vr/perf, which would allow the
inclusion of the entire directory, plus it'd allow us to have a single BUILD.gn
file in the future when other types of perf tests are added.

[Lei Lei, 2017/04/20 04:56:20]

Yep, I think it is better to move the BUILD.gn file to chrome/test/vr/perf, so
we don't need to update BDUILD.gn file each time when add new files for perf
tests.

It is fine to do it in another patch.

[bsheedy, 2017/04/20 17:34:56]

Done.

+    "//third_party/gvr-android-sdk/test-apks/vr_services/vr_services_current.apk",
   ]
   data_deps = [
     "//chrome/android:chrome_public_apk",