MD Settings: Allow search within settings to track multiple requests separately.

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

 // Copyright 2015 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.
 
 /** @fileoverview Runs the Polymer Settings tests. */
 
 /** @const {string} Path to source root. */
 var ROOT_PATH = '../../../../../';
 
 // Polymer BrowserTest fixture.
@@ skipping 1186 matching lines @@
  */
 function CrSettingsSearchTest() {}
 
 CrSettingsSearchTest.prototype = {
   __proto__: CrSettingsBrowserTest.prototype,
 
   /** @override */
   browsePreload: 'chrome://md-settings/settings_page/settings_section.html',
 
   /** @override */
+  runAccessibilityChecks: false,

[Dan Beam, 2017/03/14 00:44:28]

i don't think we want this.  i think we want to change a specific test or just
not make a11y tests errors

[dpapad, 2017/03/14 03:28:11]

Reverted.
The way we test accessibility is weird. We test whatever is left in the DOM
after our actual test finishes. Most importantly it causes confusion when a test
fails, because when it fails different things are left in the DOM, and then
additional accessibility errors are showing, which are unrelated to the original
failure.

My thinking is that we should disable accessibility checks for all our unit
tests, and add a single test that intentionally force renders everything in the
DOM and just does a11y checks.

+
+  /** @override */
   extraLibraries: CrSettingsBrowserTest.prototype.extraLibraries.concat([
     'search_settings_test.js',
   ]),
 };
 
 TEST_F('CrSettingsSearchTest', 'All', function() {
   mocha.run();
 });
 
 /**
@@ skipping 187 matching lines @@
 
   /** @override */
   extraLibraries: CrSettingsBrowserTest.prototype.extraLibraries.concat([
     'focusable_iron_list_item_behavior_test.js',
   ]),
 };
 
 TEST_F('CrSettingsFocusableIronListItemBehavior', 'FocusTest', function() {
   mocha.run();
 });