This isn't structured properly (several classes in a single file, no proper property encapsulation, no Javadoc, no unit tests) but was written this way to simplify the dev environment requirements and followed on my thinking to producing a fully-functional version that people can actually use right away. I've also attached the scripts I used to build and run. Here is the command I used to run the full test suite against Opera:

./selenium-java.sh --browser "*opera" --testsuite ../../selenium-core-0.8.3/tests/TestSuite.html --baseurl http://mymachine/selenium-core/tests/ --out results.html

The NekoHTML parser is required in order to properly parse HTML4 syntax (used by the bulk of the Selenium Core testsuite), but on the other hand, the standard XML parser is required to properly parse XHTML syntax (produced by the Selenium IDE).

I also added support for a number of functions that exist in Core but not in the IDE.

Here is an attachment of my original GreaseMonkey prototype, which isn't anywhere nearly as functional as the Java version.

I should have also noted that the Java client driver version needs to be modified to parse the file before executing, rather than executing as it parses the file as it does now.

There are probably other problems with it too, but it should provide a decent start.

In terms of my thinking on where this could go from here:

• The GreaseMonkey script could probably get modified and incorporated into the Selenium IDE as a way to run/debug on a Selenium RC/Grid setup.

• The Java code could probably get improved upon and made part of the Java driver as a means to run Selenium IDE HTML via Selenium RC/Grid

I found a number of bugs in the code I attached here. that fail to process verify errors properly and/or to trim the HTML the same way that the IDE and Selenium Core apparently do. I'll post again when I have a fixed version of each.

Ok, here's an update. Not all tests pass now, but I'm ok with the reasons for the failures, as some don't pass in Selenium IDE anyway, and in general they're things that won't pass via selenium RC/Grid

Changes:

• Fixed numerous issues in how the tests were run
• Added coloring of results
• (Java) Fixed how results were checked
• (GM Javascript) Added support for some of the verifySelected verify types and for the store command that exist in the core but not in the remote driver protocol.
• (GM Javascript) Added support for running tests that don't have base URL in them
• (GM Javascript) Added support for specifying host, port, browser, baseurl and verbose via query parameters, which should reduce the need to modify the script.

Not done:

• (GM Javascript) reuse code from existing JS codebase
• (GM Javascript) add support for running test suites
• (GM Javascript) investigate incorporating into selenium IDE
• (Java) provide support for output being specified via XSL templates.

I'm also interested, I'd like to run the html tests along with the java tests and display aggregated results in the form of junit test reports

Daiji, could you upload the files with a license header to clarify that your work is open source before I make any modifications?

I'm also interested in running html tests on Selenium Grid.
i'm new to Selenium RC and grid...what should we do with the files included above?

Thanks,

Marcelo

I'm also interested in running html tests on Selenium Grid.
I work with a non-technical QA Team, so java tests are not an option.
I'm new to Selenium RC and grid...what should we do with the files included above?

Thanks,

Rich

This is nice-to-have for 1.0. But it will not ship with 1.0.

attached pom file for building SeleniumHtmlClient, which builds an self-contained executable htmlclient-1.0-SNAPSHOT-full.jar client

parameterization: patch adds the ability to substitute <sysprop variable="foo"/> elements in Selenese with the value of System.getProperty("foo").

Is it possible to use custom user-extensions javascript with this driver? If so, how?