html_viewer/web_view: An app for running layout-tests.

components/html_viewer/public/interfaces/layout_test_runner.mojom

Index: components/html_viewer/public/interfaces/layout_test_runner.mojom
diff --git a/chrome/test/data/extensions/api_test/service_worker/background_client/test.js b/components/html_viewer/public/interfaces/layout_test_runner.mojom
similarity index 70%
copy from chrome/test/data/extensions/api_test/service_worker/background_client/test.js
copy to components/html_viewer/public/interfaces/layout_test_runner.mojom
index 2497dc84f994bb12c39b2f79d6ec3a43e6964603..37164e541c296209f0f68abc13b892305c3b14e1 100644
--- a/chrome/test/data/extensions/api_test/service_worker/background_client/test.js
+++ b/components/html_viewer/public/interfaces/layout_test_runner.mojom
@@ -2,4 +2,8 @@
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
-chrome.tabs.create({url: chrome.extension.getURL("page.html")});
+module html_viewer;
+
+interface LayoutTestRunner {

[sky, 2015/09/03 19:31:59]

Generally we put interfaces near the implementation, not the call site. As
LayoutTestRunner is implemented in test_runner, it shouldn't be here. Putting an
interface here makes sense if html_viewer is going to implement it.

[sadrul, 2015/09/03 19:47:44]

I added it here since LayoutTestHTMLViewer in html_viewer talks to it to notify
it when the test finished. Or would it be OK to introduce a dependency on the
test-runner (whether mandoline, or another dedicated app) to
layout_test_html_viewer?

[sky, 2015/09/03 19:52:24]

I think the interface should belong with the test_runner.

+  TestFinished();
+};