Setup cross-browser selenium tests

Adds support to run specific caja tests on a selenium farm and accumulate the results in the dashboard.
The build-server specific selenium.sh file has a contract that will run its tests and deposit an xml file
of results in ant-reports/selenium

[MikeSamuel, 2009-01-22 00:31:54]

http://codereview.appspot.com/12479/diff/1/2
File tools/dashboard/dashboard.pl (right):

http://codereview.appspot.com/12479/diff/1/2#newcode109
Line 109: our $SELENIUM = "/opt/svn/selenium.sh";              requireExe $ANT;
Should this file be part of this CL?
Maybe make the requireExe line up with the others.

http://codereview.appspot.com/12479/diff/1/2#newcode119
Line 119: our $BROWSER_FORMAT = qr/\bVarZ:([\w\.\-]+)=(\d+(?:\.\d+)?)\b/;
Is this used?

http://codereview.appspot.com/12479/diff/1/2#newcode169
Line 169: extractSeleniumSummary("$REPORTS_DIR/selenium/TESTS-TestSuites.xml",
\@status_log);
wrap to 80 columns here and elsewhere

http://codereview.appspot.com/12479/diff/1/2#newcode374
Line 374: sub extractSeleniumSummary($$) {
Can you put in a comment with an example of what you're parsing.

[Jasvir, 2009-01-22 02:47:44]

http://codereview.appspot.com/12479/diff/1/2
File tools/dashboard/dashboard.pl (right):

http://codereview.appspot.com/12479/diff/1/2#newcode109
Line 109: our $SELENIUM = "/opt/svn/selenium.sh";              requireExe $ANT;
On 2009/01/22 00:31:54, MikeSamuel wrote:
> Should this file be part of this CL?
> Maybe make the requireExe line up with the others.

No - its build platform specific and simply calls the selenium farm

http://codereview.appspot.com/12479/diff/1/2#newcode119
Line 119: our $BROWSER_FORMAT = qr/\bVarZ:([\w\.\-]+)=(\d+(?:\.\d+)?)\b/;
On 2009/01/22 00:31:54, MikeSamuel wrote:
> Is this used?

No.  Removed.

http://codereview.appspot.com/12479/diff/1/2#newcode169
Line 169: extractSeleniumSummary("$REPORTS_DIR/selenium/TESTS-TestSuites.xml",
\@status_log);
On 2009/01/22 00:31:54, MikeSamuel wrote:
> wrap to 80 columns here and elsewhere

Done.

http://codereview.appspot.com/12479/diff/1/2#newcode374
Line 374: sub extractSeleniumSummary($$) {
On 2009/01/22 00:31:54, MikeSamuel wrote:
> Can you put in a comment with an example of what you're parsing.

Done.

[MikeSamuel, 2009-01-22 06:15:22]

LGTM


On 2009/01/22 02:47:44, jasvir wrote:
> http://codereview.appspot.com/12479/diff/1/2
> File tools/dashboard/dashboard.pl (right):
> 
> http://codereview.appspot.com/12479/diff/1/2#newcode109
> Line 109: our $SELENIUM = "/opt/svn/selenium.sh";              requireExe
$ANT;
> On 2009/01/22 00:31:54, MikeSamuel wrote:
> > Should this file be part of this CL?
> > Maybe make the requireExe line up with the others.
> 
> No - its build platform specific and simply calls the selenium farm
> 
> http://codereview.appspot.com/12479/diff/1/2#newcode119
> Line 119: our $BROWSER_FORMAT = qr/\bVarZ:([\w\.\-]+)=(\d+(?:\.\d+)?)\b/;
> On 2009/01/22 00:31:54, MikeSamuel wrote:
> > Is this used?
> 
> No.  Removed.
> 
> http://codereview.appspot.com/12479/diff/1/2#newcode169
> Line 169: extractSeleniumSummary("$REPORTS_DIR/selenium/TESTS-TestSuites.xml",
> \@status_log);
> On 2009/01/22 00:31:54, MikeSamuel wrote:
> > wrap to 80 columns here and elsewhere
> 
> Done.
> 
> http://codereview.appspot.com/12479/diff/1/2#newcode374
> Line 374: sub extractSeleniumSummary($$) {
> On 2009/01/22 00:31:54, MikeSamuel wrote:
> > Can you put in a comment with an example of what you're parsing.
> 
> Done.

[Jasvir, 2009-01-23 00:39:33]

@3199