[MD settings] move extra options in category settings

chrome/test/data/webui/settings/category_setting_exceptions_tests.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 Suite of tests for category-setting-exceptions. */
+cr.define('category_setting_exceptions', function() {
+  function registerTests() {
+    suite('CategorySettingExceptions', function() {
+      /**
+       * A site settings exceptions created before each test.
+       * @type {SiteSettingsExceptionsElement}
+       */
+      var testElement;

[tommycli, 2016/12/15 21:36:38]

= null; I've normally seen

[dschuyler, 2016/12/16 20:39:45]

Is there a reason null is better than undefined here?

+
+      // Import necessary html before running suite.
+      suiteSetup(function() {
+        return PolymerTest.importHtml(
+           'chrome://md-settings/site_settings/category_setting_exceptions.html');
+      });
+
+      // Initialize a category-setting-exceptions before each test.
+      setup(function() {
+        browserProxy = new TestSiteSettingsPrefsBrowserProxy();
+        settings.SiteSettingsPrefsBrowserProxyImpl.instance_ = browserProxy;
+        PolymerTest.clearBody();
+        testElement = document.createElement('category-setting-exceptions');
+        document.body.appendChild(testElement);
+      });
+
+      test('create category-setting-exceptions', function() {
+        // The category-setting-exceptions is mainly a container for site-lists.
+        // There's not much that merits testing.
+        assertTrue(!!testElement);

[tommycli, 2016/12/15 21:36:38]

Well if there's legitimately nothing that merits testing we can just delete this
whole file. I agree (btw) that there's not much worth testing there.

[dschuyler, 2016/12/16 20:39:45]

Acknowledged.

+      });
+    });
+  }
+
+  return {
+    registerTests: registerTests,
+  };
+});