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

chrome/test/data/firefox3_profile/README

Index: chrome/test/data/firefox3_profile/README
diff --git a/chrome/test/data/firefox3_profile/README b/chrome/test/data/firefox3_profile/README
new file mode 100644
index 0000000000000000000000000000000000000000..456d14684577bd9996982160a17ace8c6a228afb
--- /dev/null
+++ b/chrome/test/data/firefox3_profile/README
@@ -0,0 +1,29 @@
+The search.sqlite contains a table named |engine_data| which holds information
+about search engines. The table's data has been modified for the sake of
+testing. The original content of |engine_data| looked as follows:
+
+id    engineid                     name     value
+--    -------------------------    -----    -----
+10    [app]/google.xml             order    1
+11    [app]/yahoo.xml              order    2
+12    [app]/amazondotcom.xml       order    3
+13    [app]/answers.xml            order    4
+14    [app]/creativecommons.xml    order    5
+15    [app]/eBay.xml               order    6
+16    [profile]/flickr-tags.xml    order    7
+17    [profile]/imdb.xml           order    8
+18    [profile]/webster.xml        order    9
+19    [app]/wikipedia.xml          order    10
+
+The |engineid| contains [app]/<name>.xml or [profile]/<name>.xml where
+the [app] and [profile] need to be replaced with the actual app or profile
+path. The actual app or profile path varies with operating system. To make

[Ilya Sherman, 2014/06/06 04:15:42]

Do the app and profile paths vary by operating system, even in the test setup? 
Looking more closely at the test code, it looks like SetUp() creates a temporary
directory, and profile and app directories within it.  Do these app and profile
paths not get used?

[Tapu Ghose, 2014/06/15 04:19:49]

You are right. [app] and [profle] should not vary by operating system in test
setup.
Update test code to make use of app and profile paths.

+the browser test independant of machine's environment, [app] and [profile]
+is replaced with relative path as follows:
+
+[app] => ./chrome/test/data/firefox3_profile/searchplugins/default
+[profile] => ./chrome/test/data/firefox3_profile/searchplugins/installed

[Ilya Sherman, 2014/06/06 04:15:42]

What is this path relative to?  Since the test code copies all of the files over
to a temporary directory, it seems unnecessary to have the
"chrome/test/data/firefox3_profile" prefix.

[Ilya Sherman, 2014/06/06 04:15:42]

Also, I've realized that the test code expects the search engine XML files to
all live in a common location.  Rather than adding them once to
//chrome/test/data/firefox3_profile/searchplugins and again to
//chrome/test/data/firefox_profile/searchplugins, you could add them to
//chrome/test/data/firefox_searchplugins.  You'd then have the test code copy
over the contents of this directory to {tempdir}/app/searchplugins.  Does that
make sense?

[Tapu Ghose, 2014/06/15 04:19:49]

Completely agree with you. All search engine XML files are placed in
//chrome/test/data/firefox_searchplugins and updated test code
accordingly.

[Tapu Ghose, 2014/06/15 04:19:49]

The path was relative to /src. But now I made use of temporary directory.

+
+To respect the relative path in test data, all default and installed search
+engines XMLs are placed in searchplugins/default and searchplugins/installed
+directory respectively.