[chromedriver] Update Java tests to latest selenium release, 2.31.

[chromedriver] Update Java tests to latest selenium release, 2.31.

Also change test runner to filter tests based on the Google Test (C++) filter
format. Include all standard selenium java tests, even those that were
ignored for Chrome (regardless of reason).
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=192756

[kkania, 2013-04-05 01:00:30]

I won't commit this until my other CL has been approved

[chrisgao (Use stgao instead), 2013-04-05 15:41:09]

lgtm with nits.

https://codereview.chromium.org/13688002/diff/1004/README.chromium
File README.chromium (right):

https://codereview.chromium.org/13688002/diff/1004/README.chromium#newcode22
README.chromium:22: - Zip all of common into common.zip.
How about adding commands for all steps?

https://codereview.chromium.org/13688002/diff/1004/patch.diff
File patch.diff (right):

https://codereview.chromium.org/13688002/diff/1004/patch.diff#newcode71
patch.diff:71: +    String filter = System.getProperty("filter", ".*");
I think it is OK to create the positive/negative patterns here. But it would be
better to create them in a setup function like to original "only_run" and
"method".
Because this method is invoked for each of all 770+ tests.

https://codereview.chromium.org/13688002/diff/1004/patch.diff#newcode79
patch.diff:79: +    for (int i = 0; i < positivePatterns.length; i++) {
Test against negative patterns and then the positive ones will make the code
simpler.

[kkania, 2013-04-05 17:31:26]

done, also added to patch stuff for actually running the HTML5 java tests. A lot
of these tests do @Before assumeTrue which fails, and then automatically passes
the test.

https://codereview.chromium.org/13688002/diff/1004/README.chromium
File README.chromium (right):

https://codereview.chromium.org/13688002/diff/1004/README.chromium#newcode22
README.chromium:22: - Zip all of common into common.zip.
On 2013/04/05 15:41:09, chrisgao wrote:
> How about adding commands for all steps?

Done.

https://codereview.chromium.org/13688002/diff/1004/patch.diff
File patch.diff (right):

https://codereview.chromium.org/13688002/diff/1004/patch.diff#newcode71
patch.diff:71: +    String filter = System.getProperty("filter", ".*");
On 2013/04/05 15:41:09, chrisgao wrote:
> I think it is OK to create the positive/negative patterns here. But it would
be
> better to create them in a setup function like to original "only_run" and
> "method".
> Because this method is invoked for each of all 770+ tests.

keeping it here; it doesn't really matter, as you say. i want the patch to be as
simple as possible

https://codereview.chromium.org/13688002/diff/1004/patch.diff#newcode79
patch.diff:79: +    for (int i = 0; i < positivePatterns.length; i++) {
On 2013/04/05 15:41:09, chrisgao wrote:
> Test against negative patterns and then the positive ones will make the code
> simpler.

Done.

[kkania, 2013-04-06 16:07:38]

Committed patchset #2 manually as r192756 (presubmit successful).