Cancel client auth requests when not promptable.

chrome/browser/extensions/extension_apitest.h

Index: chrome/browser/extensions/extension_apitest.h
diff --git a/chrome/browser/extensions/extension_apitest.h b/chrome/browser/extensions/extension_apitest.h
index 6717cbb8ba16dd40e4782803bbfa3af6f9066c32..873cf7f6905c8da7f5cb4d8a2c1b6d979e7592f4 100644
--- a/chrome/browser/extensions/extension_apitest.h
+++ b/chrome/browser/extensions/extension_apitest.h
@@ -106,6 +106,11 @@ class ExtensionApiTest : public ExtensionBrowserTest {
                            const std::string& page_url,
                            int flags);
 
+  // Same as RunExtensionSubtest, but with a custom argument.
+  bool RunExtensionSubtestWithArg(const std::string& extension_name,
+                                  const std::string& page_url,
+                                  const char* custom_arg);

[asargent_no_longer_on_chrome, 2015/03/03 00:10:30]

A better to do this instead of adding a new method override to this class is
with an ExtensionTestMessageListener that you set up inside your
BackgroundXhrTlsClientAuth test. (See
extensions/test/extension_test_message_listener.h )


E.g.

ExtensionTestMessageListener listener(true);

...

EXPECT_TRUE(listener.WaitUntilSatisfied());
listener.Reply( < some message here that you would have put in custom_arg>);


From your javascript code, you can get access to this data by doing:


chrome.test.sendMessage("whatever", function(response) {
  // response is whatever string we sent via listener.Reply in C++
  // do something with it
});

[davidben, 2015/03/05 20:01:52]

Done. (I just snuck the custom arg through the URL since that seemed easier.
Saves a round-trip.)

+
   // Load |page_url| and wait for pass / fail notification from the extension
   // API on the page.
   bool RunPageTest(const std::string& page_url);