Update Autofill Private API to provide a list of available countries.

chrome/browser/extensions/api/autofill_private/autofill_private_apitest.cc

Index: chrome/browser/extensions/api/autofill_private/autofill_private_apitest.cc
diff --git a/chrome/browser/extensions/api/autofill_private/autofill_private_apitest.cc b/chrome/browser/extensions/api/autofill_private/autofill_private_apitest.cc
index adb161b6447a8d5a12c6777cae35c5b5ee4da1fe..ad3fa6172ddbddc89774872aff9030880da4edc2 100644
--- a/chrome/browser/extensions/api/autofill_private/autofill_private_apitest.cc
+++ b/chrome/browser/extensions/api/autofill_private/autofill_private_apitest.cc
@@ -46,6 +46,10 @@ IN_PROC_BROWSER_TEST_F(AutofillPrivateApiTest, SaveAddress) {
   EXPECT_TRUE(RunAutofillSubtest("saveAddress")) << message_;
 }
 
+IN_PROC_BROWSER_TEST_F(AutofillPrivateApiTest, GetCountryList) {
+  EXPECT_TRUE(RunAutofillSubtest("getCountryList")) << message_;

[Devlin, 2016/06/10 18:25:11]

semi-drive-by - do all these really need separate browser tests?  Browser tests
are expensive, and most extension APIs are designed to be able to run multiple
tests in a single browsertest to avoid startup/shutdown costs.  Alternatively,
and even better, it looks like a lot of these could just be unittests.

I don't wanna block this CL on that (unless you're up for it ;)), but as food
for thought, and maybe a TODO.

[hcarmona, 2016/06/10 20:42:51]

Sounds good, I've added a TODO at the top of this file to investigate
converting to unittests.

+}
+
 IN_PROC_BROWSER_TEST_F(AutofillPrivateApiTest, GetAddressComponents) {
   EXPECT_TRUE(RunAutofillSubtest("getAddressComponents")) << message_;
 }