DevTools: create test infrastructure so devtools drives the test

third_party/WebKit/Source/devtools/front_end/integration_test_runner/module.json

Index: third_party/WebKit/Source/devtools/front_end/integration_test_runner/module.json
diff --git a/third_party/WebKit/Source/devtools/front_end/integration_test_runner/module.json b/third_party/WebKit/Source/devtools/front_end/integration_test_runner/module.json
new file mode 100644
index 0000000000000000000000000000000000000000..14f028e2e6bef3578de0f8552c780a6e81dff252
--- /dev/null
+++ b/third_party/WebKit/Source/devtools/front_end/integration_test_runner/module.json
@@ -0,0 +1,14 @@
+{
+  "dependencies": [
+    "test_runner",

[dgozman, 2017/04/25 21:08:28]

Why not merge this module into test_runner?

[chenwilliam, 2017/06/15 01:01:05]

We can't run certain modules in test_runner (unit tests). Joel has details (I
forgot :o)

+    "sdk"
+  ],
+  "test_dependencies": [

[chenwilliam, 2017/04/25 01:09:07]

I want test writers to control the lifetime of loading modules, so I created
this to keep the dependency preprocessor happy.

[dgozman, 2017/04/25 21:08:28]

Why should tests worry about modules lifetime?

[chenwilliam, 2017/06/15 01:01:05]

I want to avoid loading all modules up-front to avoid the startup cost. I don't
have a concrete case - but I imagine someone might want a test where clicking on
a panel properly loads it. If we eagerly load modules (e.g. text editor) in the
case of console, we might miss some edge cases (e.g. console properly shows
messages before text editor has loaded).

+    "console",
+    "console_model"
+  ],
+  "scripts": [
+    "ConsoleTestRunner.js",
+    "IntegrationTestRunner.js"
+  ]
+}