MD Settings: fix improper use of prefs in tests

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

Index: chrome/test/data/webui/settings/on_startup_browsertest.js
diff --git a/chrome/test/data/webui/settings/on_startup_browsertest.js b/chrome/test/data/webui/settings/on_startup_browsertest.js
index 04882f82ffac71d8e75a3ca37744f2e55997cfc8..7e098ddf3711cc6f30b59638f6aab617937bc506 100644
--- a/chrome/test/data/webui/settings/on_startup_browsertest.js
+++ b/chrome/test/data/webui/settings/on_startup_browsertest.js
@@ -52,20 +52,10 @@ TEST_F('OnStartupSettingsBrowserTest', 'uiTests', function() {
   };
 
   suite('OnStartupHandler', function() {
-    var fakePrefs = [{
-      key: 'session.restore_on_startup',
-      type: chrome.settingsPrivate.PrefType.NUMBER,
-      value: 1234,
-    }];
-
     suiteSetup(function() {
       settingsPrefs = document.querySelector('cr-settings').$$(
           'settings-prefs');
       assertTrue(!!settingsPrefs);
-      CrSettingsPrefs.resetForTesting();
-      settingsPrefs.resetForTesting();
-      var fakeApi = new settings.FakeSettingsPrivate(fakePrefs);
-      settingsPrefs.initializeForTesting(fakeApi);
       return CrSettingsPrefs.initialized;
     });