MD Settings: fix auto-focus on sync page.

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

Index: chrome/test/data/webui/settings/cr_settings_interactive_ui_tests.js
diff --git a/chrome/test/data/webui/settings/cr_settings_interactive_ui_tests.js b/chrome/test/data/webui/settings/cr_settings_interactive_ui_tests.js
index 9f4b7e31d419cca07d0e81eaba275a239f12a112..a6f11751991be1285e04996fcb69dd89635f3340 100644
--- a/chrome/test/data/webui/settings/cr_settings_interactive_ui_tests.js
+++ b/chrome/test/data/webui/settings/cr_settings_interactive_ui_tests.js
@@ -66,6 +66,30 @@ TEST_F('CrSettingsFocusRowBehavior', 'FocusTest', function() {
 });
 
 
+/**
+ * Test fixture for Sync Page.
+ * @constructor
+ * @extends {CrSettingsInteractiveUITest}
+ */
+function CrSettingsSyncPageTest() {}
+
+CrSettingsSyncPageTest.prototype = {
+  __proto__: CrSettingsInteractiveUITest.prototype,

[dpapad, 2017/06/14 01:02:00]

Does the new test have to be an interactive UI test? Asking because we already
have tests for sync_page.html, at
https://cs.chromium.org/chromium/src/chrome/test/data/webui/settings/cr_setti...

It is currently a bit confusing that we have two files that test the same
element,

people_page_sync_page_test.js (existing)
settings_sync_page_test.js (new in this CL)

So I suggest to either
1) Run your new test as a normal test and move the test in the existing file.
2) If 1 not possible, maybe still move the test in the existing file, and use
mocha.grep() at line 80 to only run your new test case as an interactive ui
test.
3) If not 1 or 2, rename the files to be more consistent/descriptive?

+
+  /** @override */
+  browsePreload: 'chrome://md-settings/people_page/sync_page.html',
+
+  /** @override */
+  extraLibraries: CrSettingsInteractiveUITest.prototype.extraLibraries.concat([
+    'settings_sync_page_test.js',
+  ]),
+};
+
+TEST_F('CrSettingsSyncPageTest', 'All', function() {
+  mocha.run();
+});
+
+
 /**
  * @constructor
  * @extends {CrSettingsInteractiveUITest}