[MD settings] unit test for settings-menu

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

+// Copyright 2016 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 tests for the settings menu. */
+
+cr.define('settings_menu', function() {
+  function registerSettingsMenuTest() {
+    var settingsMenu = null;
+
+    suite('SettingsMenu', function() {
+      setup(function() {
+        PolymerTest.clearBody();
+        settingsMenu = document.createElement('settings-menu');
+        document.body.appendChild(settingsMenu);
+      });
+
+      teardown(function() { settingsMenu.remove(); });
+
+      test('defaultToBasic', function() {
+        settingsMenu.currentRoute = {page: 'basic', section: '', subpage: []};
+        assertFalse(!!settingsMenu.$.advancedPage.opened);

[dpapad, 2016/05/05 00:11:29]

paper-submenu#opened property is a boolean already, so there is no need to
double-negate it (which is a trick for converting a non-boolean to a boolean
value). Same below.

[dschuyler, 2016/05/05 00:23:49]

Done.

+        assertTrue(!!settingsMenu.$.basicPage.opened);
+      });
+
+      test('openAdvanced', function() {
+        settingsMenu.currentRoute = {
+          page: 'advanced', section: '', subpage: []
+        };
+        assertTrue(!!settingsMenu.$.advancedPage.opened);
+        assertFalse(!!settingsMenu.$.basicPage.opened);
+      });
+    });

[dpapad, 2016/05/05 00:11:29]

Optional: Can we add a test for the case where currentRoute has a 'section' and
assert that the correct entry is "selected"?

[dschuyler, 2016/05/05 00:23:49]

Done.

+  }
+
+  return {
+    registerTests: function() {
+      registerSettingsMenuTest();
+    },
+  };
+});