Configuration file for Chrome perf and endure tests.

chrome/test/functional/perf.cfg

Index: chrome/test/functional/perf.cfg
diff --git a/chrome/test/functional/perf.cfg b/chrome/test/functional/perf.cfg
new file mode 100644
index 0000000000000000000000000000000000000000..62dcf5f201b25026605dfd54097f5c54dc718518
--- /dev/null
+++ b/chrome/test/functional/perf.cfg
@@ -0,0 +1,23 @@
+# Configuration file for pyauto perf tests.
+# This file is used to specify google account credential and

[dennis_jeffrey, 2012/08/15 01:21:17]

credential --> credentials

[fdeng1, 2012/08/16 17:42:49]

Done.

+# customized google account, gmail, docs, plus urls if you don't want to use
+# the public urls of these services. It is formated as a python dictionary.

[dennis_jeffrey, 2012/08/15 01:21:17]

formated --> formatted

[fdeng1, 2012/08/16 17:42:49]

Done.

+#
+# If you are external to Google, you must use this file.
+# If you are internal to Google, you can skip this file and tests
+# will try to use internal credential file.  
+# Example:
+#{
+#  "username": "my_username",
+#  "password": "my_password",
+#  "google_account_url": "https://my-google-account-server",
+#  # Settings bellow are only effective for perf_endure.py

[fdeng1, 2012/08/11 00:11:27]

Do we want to allow perf.py to use alternative gmail/plus/docs urls?

[dennis_jeffrey, 2012/08/15 01:21:17]

bellow --> below

[dennis_jeffrey, 2012/08/15 01:21:17]

probably not.  they should just be able to use customized login credentials. 
The custom webapp URLS are more important for Chrome Endure since other webapp
teams will likely need to run those tests.

[fdeng1, 2012/08/16 17:42:49]

Done.

+#  "gmail_url": "https://my-gmail-server",
+#  "plus_url": "https://my-plus-server",
+#  "docs_url": "https://my-docs-server",
+#}
+# If the url for a google service is not specified, the public one
+# will be used.
+{
+  # Empty configuration.

[dennis_jeffrey, 2012/08/15 01:21:17]

Rather than having a comment above to show all the possible config options (and
hoping the comment is kept up-to-date as the code changes), I think it's better
to explicitly put all the config options here in the actual dictionary.  We can
just give them a default value of None and tell the user to override them if
needed.  For example:

{
  'username': None,  # Set to custom username if desired.
  'password': None,  # Set to custom password if desired.
  ... 
}

[fdeng1, 2012/08/16 17:42:49]

Done.

+}