Add WebVR WebVR E2E test capabilities via Android instrumentation

chrome/test/data/android/webvr_instrumentation/resources/webvr_e2e.js

Index: chrome/test/data/android/webvr_instrumentation/resources/webvr_e2e.js
diff --git a/chrome/test/data/android/webvr_instrumentation/resources/webvr_e2e.js b/chrome/test/data/android/webvr_instrumentation/resources/webvr_e2e.js
new file mode 100644
index 0000000000000000000000000000000000000000..e04500338fe0d7a8e2bf40a9a728ef45022713df
--- /dev/null
+++ b/chrome/test/data/android/webvr_instrumentation/resources/webvr_e2e.js
@@ -0,0 +1,42 @@
+// Copyright 2017 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.
+
+var testPassed = false;
+var resultString = "";
+var asyncCounter = 0;
+var javascriptDone = false;
+var vrDisplayPromiseDone = false;
+
+function finishJavascriptStep() {
+  javascriptDone = true;
+}
+
+function checkResultsForFailures(tests, harness_status) {
+  testPassed = true;
+  if (harness_status["status"] != 0) {
+    testPassed = false;
+    resultString += "Harness failed due to " +
+                    (harness_status["status"] == 1 ? "error" : "timeout")
+                    + ". ";
+  }
+  for (var test in tests) {
+    let passed = (tests[test]["status"] == 0);
+    if (!passed) {
+      testPassed = false;
+      resultString += "FAIL ";
+    } else {
+      resultString += "PASS ";
+    }
+    resultString += tests[test]["name"] +
+                    (passed ? "" : (": " + tests[test]["message"])) +
+                    ". ";

[Lei Lei, 2017/02/16 22:04:50]

How about setting resultString to JSON.stringify(tests)? Since you already have
testPassed variable to indicate if tests pass or not. The resultString can
include all the information for debug.

[bsheedy, 2017/02/16 23:30:14]

I feel like that ends up being too verbose. For a single test,
JSON.stringify(tests) results in:

[{"name":"NFC scan fires the vrdisplayactivate
event","phase":3,"status":0,"timeout_id":null,"index":1,"properties":{},"timeout_length":null,"message":null,"stack":null,"steps":[],"cleanup_callbacks":[],"_structured_clone":{"name":"NFC
scan fires the vrdisplayactivate
event","properties":{},"PASS":0,"FAIL":1,"TIMEOUT":2,"NOTRUN":3,"status":0,"message":null,"stack":null,"index":1}}]

compared to the current resultString:

PASS NFC scan fires the vrdisplayactivate event.

Since resultString is used as the description for the Java assert at the very
end of a test, it'll get printed out anytime testharness.js reports a failure,
so I'd prefer to keep it from being too long.

[Lei Lei, 2017/02/17 00:18:14]

It is fine to keep it short, what is the message if the test is failed? Does it
include stack?

[bsheedy, 2017/02/17 17:58:10]

An example of a test failing when reaching an assert_unreached("Some
description"):

FAIL Test pose data in unfocused tab: assert_unreached: Some description Reached
unreachable code.

+  }
+}
+
+add_completion_callback( (tests, harness_status) => {
+  checkResultsForFailures(tests, harness_status);
+  console.debug("Test result: " + (testPassed ? "Pass" : "Fail"));
+  console.debug("Test result string: " + resultString);
+  finishJavascriptStep();
+});