Parsed search.json for importing search engine settings from FireFox.

chrome/test/data/firefox_profile/README

Index: chrome/test/data/firefox_profile/README
diff --git a/chrome/test/data/firefox_profile/README b/chrome/test/data/firefox_profile/README
new file mode 100644
index 0000000000000000000000000000000000000000..f2f08dbcf9babb33baea0f16b34937569204d8df
--- /dev/null
+++ b/chrome/test/data/firefox_profile/README
@@ -0,0 +1,19 @@
+This directory is created to hold test data for Firefox importer browser tests.
+
+Since Firefox 3.5, instead of search.sqlite, all search engines are stored in
+search.json. The test data in this directory is intended for Firefox 3.5 and
+later.
+
+The search.json is grabbed from profile directory of Firefox 28.0 that runs in
+Ubuntu 12.04.4 LTS. To make this test search.json light weight, the keys
+|_iconURL| and |_iconMapObj| are removed from each search engines' dictionary.
+Moreover, each list of |engines| is updated to respect existing |kFirefoxKeywords|.

[Ilya Sherman, 2014/05/06 04:21:49]

nit: Please wrap to 80 columns per line.

[Tapu Ghose, 2014/05/06 05:18:53]

I should be more careful. Usually, I run "git cl format" before committing. But
occasionally it fails to format the codes.

[Ilya Sherman, 2014/05/06 19:00:12]

Yeah, I think "git cl format" only formats C++ files.  Thanks for fixing the
wrapping here :)

+Please NOTE that values of |filePath| is dependant on workstation. They NEED to be

[Ilya Sherman, 2014/05/06 04:21:49]

nit: Ditto here.

+updated in order to pass the test in corresponding workstation.

[Ilya Sherman, 2014/05/06 04:21:49]

Hmm.  Do you mean that the test you're adding will only run correctly on a
single platform?  If so, it would be good to brainstorm how to make the test
pass on all platforms.

[Tapu Ghose, 2014/05/06 05:18:53]

No. The test should run for all platforms. Here, I meant to say that if you run
the test in a try bot, then values of |filePath| in test search.json should be
updated.
In the test search.json, you can see that values of |filePath| is pointing to
some of my local machine's directories. The values of |filePath| is the location
of xml files for Firefox's search engines.

[Ilya Sherman, 2014/05/06 19:00:12]

Is it possible to include the XML files in the test directory, and to use
relative file paths to those XML files?  The test should be able to run
successfully on all platforms without any changes to the data files.  Once the
test code is checked in to the tree, it will be run automatically (so that it
can catch regressions :)), so we need to make sure that it works everywhere.

Currently, the try bots from patch set 4 are showing failures on all platforms. 
(There are also many unrelated failures that you can safely ignore.  Our
infrastructure has lots of sources of flaky failures, which folks are gradually
working on fixing.)  Do those results give you enough information to debug and
implement fixes?

+
+All other files are grabbed from
+/src/chrome/test/data/firefox35_profile because
+
+1) They respect the existing |kFirefoxBookmarks|, |kFirefoxPasswords|
+of firefox_importer_browsertests.cc.
+2) Unlike search.sqlite, their behavior have not changed.