MD Settings: Manage search engines 3/3, hooking up UI.

chrome/test/data/webui/settings/cr_settings_browsertest.js

Index: chrome/test/data/webui/settings/cr_settings_browsertest.js
diff --git a/chrome/test/data/webui/settings/cr_settings_browsertest.js b/chrome/test/data/webui/settings/cr_settings_browsertest.js
index 6790547a46ce942fbbbcf6073391fe7cf4773692..9f57c7b6ac58cee140aa11acaa4a94a5c95730cf 100644
--- a/chrome/test/data/webui/settings/cr_settings_browsertest.js
+++ b/chrome/test/data/webui/settings/cr_settings_browsertest.js
@@ -36,6 +36,7 @@ CrSettingsBrowserTest.prototype = {
     'prefs_test_cases.js',
     'prefs_tests.js',
     'reset_page_test.js',
+    'search_engines_page_test.js',
     'site_details_tests.js',
     'site_details_permission_tests.js',
     'site_list_tests.js',
@@ -69,9 +70,15 @@ TEST_F('CrSettingsBrowserTest', 'MAYBE_CrSettingsTest', function() {
   mocha.run();
 });
 
-
 TEST_F('CrSettingsBrowserTest', 'ResetPage', function() {
   settings_reset_page.registerDialogTests();
   settings_reset_page.registerBannerTests();
   mocha.run();
 });
+
+TEST_F('CrSettingsBrowserTest', 'SearchEnginesPage', function() {
+  settings_search_engines_page.registerDialogTests();
+  settings_search_engines_page.registerEntryTests();
+  settings_search_engines_page.registerPageTests();

[Dan Beam, 2016/02/17 02:21:35]

i don't know that you should be doing all of this in one TEST_F()

[dpapad, 2016/02/17 03:22:36]

Any reasons why not? The tests share a bit of setup (like defining the
TestBrowserProxy class), and it would take longer to run if we split them. So
far they seem to be doing a good job not interfering with each other, so I
prefer to keep one TEST_F for each sub-page (similarly to ResetPage tests
above).

+  mocha.run();
+});