Implement an initial extension settings API.

chrome/browser/extensions/extension_settings_apitest.cc

Index: chrome/browser/extensions/extension_settings_apitest.cc
diff --git a/chrome/browser/extensions/extension_settings_apitest.cc b/chrome/browser/extensions/extension_settings_apitest.cc
new file mode 100644
index 0000000000000000000000000000000000000000..45fd9da1032ef4bad05e29e04919fabee9c4d7dd
--- /dev/null
+++ b/chrome/browser/extensions/extension_settings_apitest.cc
@@ -0,0 +1,24 @@
+// Copyright (c) 2011 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.
+
+#include "base/command_line.h"
+#include "chrome/browser/extensions/extension_apitest.h"
+#include "chrome/common/chrome_switches.h"
+#include "net/base/mock_host_resolver.h"
+
+class ExtensionSettingsApiTest : public ExtensionApiTest {
+ public:
+  virtual void SetUpInProcessBrowserTestFixture() {
+    ExtensionApiTest::SetUpInProcessBrowserTestFixture();
+    // TODO(kalman): necessary?
+    host_resolver()->AddRule("*", "127.0.0.1");

[Mihai Parparita -not on Chrome, 2011/06/21 23:40:11]

I don't think this is necessary.

[not at google - send to devlin, 2011/06/22 09:40:38]

Done.

+    ASSERT_TRUE(StartTestServer());

[Mihai Parparita -not on Chrome, 2011/06/21 23:40:11]

We generally put this in the test case, though I don't think you need a test
server at all (we use that when testing the interaction of extensions with page
contents, but your tests lives entirely in the extension process).

[not at google - send to devlin, 2011/06/22 09:40:38]

Done.  Yeah this just came from one of the tests I copied, forgot to come back
to it.

+  }
+};
+
+IN_PROC_BROWSER_TEST_F(ExtensionSettingsApiTest, Settings) {
+  CommandLine::ForCurrentProcess()->AppendSwitch(
+      switches::kEnableExperimentalExtensionApis);
+  ASSERT_TRUE(RunExtensionTest("settings")) << message_;
+}