Use extension match pattern syntax in content settings extension API

chrome/browser/extensions/extension_content_settings_unittest.cc

Index: chrome/browser/extensions/extension_content_settings_unittest.cc
diff --git a/chrome/browser/extensions/extension_content_settings_unittest.cc b/chrome/browser/extensions/extension_content_settings_unittest.cc
new file mode 100644
index 0000000000000000000000000000000000000000..2ae8554969168a5009a579b74a1e7e2922ea5670
--- /dev/null
+++ b/chrome/browser/extensions/extension_content_settings_unittest.cc
@@ -0,0 +1,29 @@
+// 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 "testing/gtest/include/gtest/gtest.h"
+
+#include "chrome/browser/extensions/extension_content_settings_helpers.h"
+
+namespace helpers = extension_content_settings_helpers;
+
+TEST(ExtensionContentSettingsHelpersTest, ParseExtensionPattern) {
+  const struct {
+    const char* extension_pattern;
+    const char* content_settings_pattern;
+  } kTestPatterns[] = {
+    { "<all_urls>", "*" },
+    { "*://*.google.com/*", "[*.]google.com" },
+    { "http://www.example.com/*", "http://www.example.com:80" },
+    { "file:///foo/bar/baz", "file:///foo/bar/baz" },

[Matt Perry, 2011/06/24 18:53:58]

could you add a few more cases (test port and https)? and another test for error
cases (http://foo.com/path and file://with/wildcards*)

[Bernhard Bauer, 2011/06/28 16:46:31]

Done.

+  };
+  for (size_t i = 0; i < ARRAYSIZE_UNSAFE(kTestPatterns); ++i) {
+    std::string error;
+    std::string pattern_str = helpers::ParseExtensionPattern(
+        kTestPatterns[i].extension_pattern, &error).ToString();
+    EXPECT_STREQ(kTestPatterns[i].content_settings_pattern, pattern_str.c_str())
+        << "Unexpected error parsing " << kTestPatterns[i].extension_pattern
+        << ": " << error;
+  }
+}